2 # The purpose of this file is to define network related paramters that are
3 # referenced elsewhere in the manifests for this site.
5 # TODO: Include bare metal host FQDN naming standards
6 # TODO: Include ingress FQDN naming standards
7 schema: pegleg/CommonAddresses/v1
9 schema: metadata/Document/v1
10 name: common-addresses
14 storagePolicy: cleartext
17 # NEWSITE-CHANGEME: The interface that calico will use. Update if your
18 # logical bond interface name or calico VLAN have changed from the reference
20 # This should be whichever
21 # bond and VLAN number specified in networks/physical/networks.yaml for the Calico
22 # network. E.g. VLAN 22 for the calico network as a member of bond0, you
23 # would set "interface=bond0.22" as shown here.
24 ip_autodetection_method: interface=bond0.22
26 # etcd service IP address
27 service_ip: 10.96.232.136
30 # Kubernetes cluster domain. Do not change. This is internal to the cluster.
31 cluster_domain: cluster.local
33 service_ip: 10.96.0.10
34 # List of upstream DNS forwards. Verify you can reach them from your
35 # environment. If so, you should not need to change them.
40 # Repeat the same values as above, but formatted as a common separated
42 upstream_servers_joined: 8.8.8.8,8.8.4.4,208.67.222.222
43 # NEWSITE-CHANGEME: FQDN for ingress (i.e. "publicly facing" access point)
44 # Choose FQDN according to the ingress/public FQDN naming conventions at
45 # the top of this document.
46 ingress_domain: airship-seaworthy.atlantafoundry.com
49 # NEWSITE-CHANGEME: Update with the hostname for the node which will take on
50 # the Genesis role. Refer to the hostname naming stardards in
51 # networks/physical/networks.yaml
52 # NOTE: Ensure that the genesis node is manually configured with this
53 # hostname before running `genesis.sh` on the node.
54 hostname: cab23-r720-11
55 # NEWSITE-CHANGEME: Calico IP of the Genesis node. Use the "start" value for
56 # the calico network defined in networks/physical/networks.yaml for this IP.
60 # NEWSITE-CHANGEME: Update with the "start" value/IP of the static range
61 # defined for the pxe network in networks/physical/networks.yaml
66 api_service_ip: 10.96.0.1
68 etcd_service_ip: 10.96.0.2
69 # k8s pod CIDR (network which pod traffic will traverse)
70 pod_cidr: 10.97.0.0/16
71 # k8s service CIDR (network which k8s API traffic will traverse)
72 service_cidr: 10.96.0.0/16
73 # misc k8s port settings
76 service_node_port_range: 30000-32767
83 # NEWSITE-CHANGEME: A list of nodes (apart from Genesis) which act as the
84 # control plane servers. Ensure that this matches the nodes with the 'masters'
85 # tags applied in baremetal/nodes.yaml
87 - hostname: cab23-r720-12
88 - hostname: cab23-r720-13
89 - hostname: cab23-r720-14
91 # NEWSITE-CHANGEME: Environment proxy information.
92 # NOTE: Reference Airship sites do not deploy behind a proxy, so this proxy section
93 # should be commented out.
94 # However if you are in a lab that requires proxy, ensure that these proxy
95 # settings are correct and reachable in your environment; otherwise update
96 # them with the correct values for your environment.
105 maas_proxy: 31800 # hardcoded in MAAS
110 # comma separated NTP server list. Verify that these upstream NTP servers are
111 # reachable in your environment; otherwise update them with the correct
112 # values for your environment.
113 servers_joined: '0.ubuntu.pool.ntp.org,1.ubuntu.pool.ntp.org,2.ubuntu.pool.ntp.org,4.ubuntu.pool.ntp.org'
115 # NOTE: This will be updated soon
117 # NEWSITE-CHANGEME: FQDN for LDAP. Update to the FQDN that is
118 # relevant for your type of deployment (test vs prod values, etc).
119 base_url: 'ldap.example.com'
120 # NEWSITE-CHANGEME: As above, with the protocol included to create a full URI
121 url: 'ldap://ldap.example.com'
122 # NEWSITE-CHANGEME: Update to the correct expression relevant for this
123 # deployment (test vs prod values, etc)
124 auth_path: DC=test,DC=test,DC=com?sAMAccountName?sub?memberof=CN=test,OU=Application,OU=Groups,DC=test,DC=test,DC=com
125 # NEWSITE-CHANGEME: Update to the correct AD group that contains the users
126 # relevant for this deployment (test users vs prod users/values, etc)
128 # NEWSITE-CHANGEME: Update to the correct subdomain for your type of
129 # deployment (test vs prod values, etc)
131 # NEWSITE-CHANGEME: Update to the correct domain for your type of
132 # deployment (test vs prod values, etc)
137 # NEWSITE-CHANGEME: CIDRs for Ceph. Update to match the network CIDR
138 # used for the `storage` network in networks/physical/networks.yaml
139 public_cidr: '10.23.23.0/24'
140 cluster_cidr: '10.23.23.0/24'
143 # NEWSITE-CHANGEME: Overlay network for VM traffic. Ensure the bond name and
144 # VLAN number are consistent with what's defined for the bond and the overlay
145 # network in networks/physical/networks.yaml
146 tunnel_device: 'bond0.24'
147 # bond which the overlay is a member of. Ensure the bond name is consistent
148 # with the bond assigned to the overlay network in
149 # networks/physical/networks.yaml
150 external_iface: 'bond0'
153 # bond which the overlay is a member of. Ensure the bond name is consistent
154 # with the bond assigned to the overlay network in
155 # networks/physical/networks.yaml
156 external_iface: 'bond0'