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={{yaml.networks.ksn.interface}}
26 # etcd service IP address
27 service_ip: 10.96.232.136
29 gateway: {{yaml.networks.ksn.gateway }}
32 public_service_cidr: {{yaml.networks.ksn.additional_cidrs[0]}}
33 ingress_vip: {{yaml.networks.ksn.ingress_vip}}
34 {% if ('peers' in yaml.networks.ksn and yaml.networks.ksn.peers is not none and yaml.networks.ksn.peers is iterable ) %}
36 {% for peer in yaml.networks.ksn.peers %}
41 ingress_vip: '{{yaml.networks.host.ingress_vip}}/32'
42 maas_vip: '{{yaml.networks.host.maas_vip}}/32'
45 # Kubernetes cluster domain. Do not change. This is internal to the cluster.
46 cluster_domain: cluster.local
48 service_ip: 10.96.0.10
49 # List of upstream DNS forwards. Verify you can reach them from your
50 # environment. If so, you should not need to change them.
52 {% for server in yaml.dns.upstream_servers %}
55 # Repeat the same values as above, but formatted as a common separated
57 upstream_servers_joined: '{{yaml.dns.upstream_servers|batch(2)|first|join(',')}}'
58 # NEWSITE-CHANGEME: FQDN for ingress (i.e. "publicly facing" access point)
59 # Choose FQDN according to the ingress/public FQDN naming conventions at
60 # the top of this document.
61 ingress_domain: {{yaml.dns.ingress_domain}}
64 # NEWSITE-CHANGEME: Update with the hostname for the node which will take on
65 # the Genesis role. Refer to the hostname naming stardards in
66 # networks/physical/networks.yaml
67 # NOTE: Ensure that the genesis node is manually configured with this
68 # hostname before running `genesis.sh` on the node.
69 hostname: {{yaml.genesis.name}}
70 # NEWSITE-CHANGEME: Calico IP of the Genesis node. Use the "start" value for
71 # the calico network defined in networks/physical/networks.yaml for this IP.
72 ip: {{yaml.genesis.ksn}}
75 # NEWSITE-CHANGEME: Update with the "start" value/IP of the static range
76 # defined for the pxe network in networks/physical/networks.yaml
77 ip: {{yaml.genesis.pxe}}
81 api_service_ip: {{yaml.kubernetes.api_service_ip}}
83 etcd_service_ip: {{yaml.kubernetes.etcd_service_ip}}
84 # k8s pod CIDR (network which pod traffic will traverse)
85 pod_cidr: {{yaml.kubernetes.pod_cidr}}
86 # k8s service CIDR (network which k8s API traffic will traverse)
87 service_cidr: {{yaml.kubernetes.service_cidr}}
88 # misc k8s port settings
91 service_node_port_range: 30000-32767
98 # NEWSITE-CHANGEME: A list of nodes (apart from Genesis) which act as the
99 # control plane servers. Ensure that this matches the nodes with the 'masters'
100 # tags applied in baremetal/nodes.yaml
102 {% for master in yaml.masters %}
103 - hostname: {{master.name}}
106 # NEWSITE-CHANGEME: Environment proxy information.
107 # NOTE: Reference Airship sites do not deploy behind a proxy, so this proxy section
108 # should be commented out.
109 # However if you are in a lab that requires proxy, ensure that these proxy
110 # settings are correct and reachable in your environment; otherwise update
111 # them with the correct values for your environment.
120 maas_proxy: 31800 # hardcoded in MAAS
123 # comma separated NTP server list. Verify that these upstream NTP servers are
124 # reachable in your environment; otherwise update them with the correct
125 # values for your environment.
126 servers_joined: '0.ubuntu.pool.ntp.org,1.ubuntu.pool.ntp.org,2.ubuntu.pool.ntp.org,4.ubuntu.pool.ntp.org'
128 # NOTE: This will be updated soon
130 # NEWSITE-CHANGEME: FQDN for LDAP. Update to the FQDN that is
131 # relevant for your type of deployment (test vs prod values, etc).
132 base_url: 'ldap.example.com'
133 # NEWSITE-CHANGEME: As above, with the protocol included to create a full URI
134 url: 'ldap://ldap.example.com'
135 # NEWSITE-CHANGEME: Update to the correct expression relevant for this
136 # deployment (test vs prod values, etc)
137 auth_path: DC=test,DC=test,DC=com?sAMAccountName?sub?memberof=CN=test,OU=Application,OU=Groups,DC=test,DC=test,DC=com
138 # NEWSITE-CHANGEME: Update to the correct AD group that contains the users
139 # relevant for this deployment (test users vs prod users/values, etc)
141 # NEWSITE-CHANGEME: Update to the correct subdomain for your type of
142 # deployment (test vs prod values, etc)
144 # NEWSITE-CHANGEME: Update to the correct domain for your type of
145 # deployment (test vs prod values, etc)
150 # NEWSITE-CHANGEME: CIDRs for Ceph. Update to match the network CIDR
151 # used for the `storage` network in networks/physical/networks.yaml
152 public_cidr: '{{yaml.networks.storage.cidr}}'
153 cluster_cidr: '{{yaml.networks.storage.cidr}}'
156 # NEWSITE-CHANGEME: Overlay network for VM traffic. Ensure the bond name and
157 # VLAN number are consistent with what's defined for the bond and the overlay
158 # network in networks/physical/networks.yaml
159 tunnel_device: '{{yaml.networks.neutron.interface}}'
160 # bond which the overlay is a member of. Ensure the bond name is consistent
161 # with the bond assigned to the overlay network in
162 # networks/physical/networks.yaml
163 external_iface: '{{yaml.networks.primary}}'
166 # bond which the overlay is a member of. Ensure the bond name is consistent
167 # with the bond assigned to the overlay network in
168 # networks/physical/networks.yaml
169 external_iface: '{{yaml.networks.primary}}'