|
| 1 | +// Module included in the following assemblies: |
| 2 | +// |
| 3 | +// * installing/installing_openstack/installing-openstack-installer-custom.adoc |
| 4 | +:_content-type: PROCEDURE |
| 5 | +[id="install-osp-deploy-dualstack_{context}"] |
| 6 | += Deploying the dual-stack cluster |
| 7 | + |
| 8 | +.Procedure |
| 9 | + |
| 10 | +. Create a network with IPv4 and IPv6 subnets. The available address modes for `ipv6-ra-mode` and `ipv6-address-mode` fields are: `stateful`, `stateless` and `slaac`. |
| 11 | ++ |
| 12 | +[NOTE] |
| 13 | +==== |
| 14 | +The dualstack network MTU must accommodate both the minimum MTU for IPv6, which is 1280, and the OVN-Kubernetes encapsulation overhead, which is 100. |
| 15 | +==== |
| 16 | ++ |
| 17 | +[NOTE] |
| 18 | +==== |
| 19 | +DHCP must be enabled on the subnets. |
| 20 | +==== |
| 21 | + |
| 22 | +. Create the API and Ingress VIPs ports. |
| 23 | + |
| 24 | +. Add the IPv6 subnet to the router to enable router advertisements. If you are using a provider network, you can enable router advertisements by adding the network as an external gateway, which also enables external connectivity. |
| 25 | + |
| 26 | + |
| 27 | +. To configure IPv4 and IPv6 address endpoints for cluster nodes, edit the `install-config.yaml` file. The following is an example of an `install-config.yaml` file. |
| 28 | + |
| 29 | +.Example `install-config.yaml` |
| 30 | + |
| 31 | +[source, yaml] |
| 32 | +---- |
| 33 | +apiVersion: v1 |
| 34 | +baseDomain: mydomain.test |
| 35 | +featureSet: TechPreviewNoUpgrade <1> |
| 36 | +compute: |
| 37 | +- name: worker |
| 38 | + platform: |
| 39 | + openstack: |
| 40 | + type: m1.xlarge |
| 41 | + replicas: 3 |
| 42 | +controlPlane: |
| 43 | + name: master |
| 44 | + platform: |
| 45 | + openstack: |
| 46 | + type: m1.xlarge |
| 47 | + replicas: 3 |
| 48 | +metadata: |
| 49 | + name: mycluster |
| 50 | +networking: |
| 51 | + machineNetwork: <2> |
| 52 | + - cidr: "192.168.25.0/24" |
| 53 | + - cidr: "fd2e:6f44:5dd8:c956::/64" |
| 54 | + clusterNetwork: <2> |
| 55 | + - cidr: 10.128.0.0/14 |
| 56 | + hostPrefix: 23 |
| 57 | + - cidr: fd01::/48 |
| 58 | + hostPrefix: 64 |
| 59 | + serviceNetwork: <2> |
| 60 | + - 172.30.0.0/16 |
| 61 | + - fd02::/112 |
| 62 | +platform: |
| 63 | + openstack: |
| 64 | + ingressVIPs: ['192.168.25.79', 'fd2e:6f44:5dd8:c956:f816:3eff:fef1:1bad'] <3> |
| 65 | + apiVIPs: ['192.168.25.199', 'fd2e:6f44:5dd8:c956:f816:3eff:fe78:cf36'] <4> |
| 66 | + controlPlanePort: <5> |
| 67 | + fixedIPs: <6> |
| 68 | + - subnet: <7> |
| 69 | + name: subnet-v4 |
| 70 | + id: subnet-v4-id |
| 71 | + - subnet: <7> |
| 72 | + name: subnet-v6 |
| 73 | + id: subnet-v6-id |
| 74 | + network: <7> |
| 75 | + name: dualstack |
| 76 | + id: network-id |
| 77 | +---- |
| 78 | + |
| 79 | +<1> Dual-stack clusters are supported only with the `TechPreviewNoUpgrade` value. |
| 80 | +<2> You must specify an IP address range in the `cidr` field for both IPv4 and IPv6 address families. |
| 81 | +<3> Specify the virtual IP (VIP) address endpoints for the Ingress VIP services to provide an interface to the cluster. |
| 82 | +<4> Specify the virtual IP (VIP) address endpoints for the API VIP services to provide an interface to the cluster. |
| 83 | +<5> Specify the dual-stack network details that are used by all the nodes across the cluster. |
| 84 | +<6> The CIDR of any subnet specified in this field must match the CIDRs listed on `networks.machineNetwork`. |
| 85 | +<7> You can specify a value for either `name` or `id`, or both. |
0 commit comments