1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-07 09:46:53 +01:00
Files
openshift-docs/modules/install-osp-deploy-dualstack.adoc
Maysa Macedo b482e89d6a Add note on NM behavior with additional networks
When using additional networks on a dual-stack cluster,
the same network manager connection would be enforced
to all the additional networks. This commit, informes
the users about that behavior and recommends an alternative
if different connections are desired.

Co-authored-by: Max Bridges <mbridges@redhat.com>
2025-02-06 16:58:54 -03:00

89 lines
3.4 KiB
Plaintext

// Module included in the following assemblies:
//
// * installing/installing_openstack/installing-openstack-installer-custom.adoc
:_mod-docs-content-type: PROCEDURE
[id="install-osp-deploy-dualstack_{context}"]
= Deploying the dual-stack cluster
For dual-stack networking in {product-title} clusters, you can configure IPv4 and IPv6 address endpoints for cluster nodes.
.Prerequisites
* You enabled Dynamic Host Configuration Protocol (DHCP) on the subnets.
.Procedure
. 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`.
+
[NOTE]
====
The dual-stack network MTU must accommodate both the minimum MTU for IPv6, which is `1280`, and the OVN-Kubernetes encapsulation overhead, which is `100`.
====
. Create the API and Ingress VIPs ports.
. 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.
. For an IPv4/IPv6 dual-stack cluster where you set IPv4 as the primary endpoint for your cluster nodes, edit the `install-config.yaml` file like the following example:
+
[source,yaml]
----
apiVersion: v1
baseDomain: mydomain.test
featureSet: TechPreviewNoUpgrade <1>
compute:
- name: worker
platform:
openstack:
type: m1.xlarge
replicas: 3
controlPlane:
name: master
platform:
openstack:
type: m1.xlarge
replicas: 3
metadata:
name: mycluster
networking:
machineNetwork: <2>
- cidr: "192.168.25.0/24"
- cidr: "fd2e:6f44:5dd8:c956::/64"
clusterNetwork: <2>
- cidr: 10.128.0.0/14
hostPrefix: 23
- cidr: fd01::/48
hostPrefix: 64
serviceNetwork: <2>
- 172.30.0.0/16
- fd02::/112
platform:
openstack:
ingressVIPs: ['192.168.25.79', 'fd2e:6f44:5dd8:c956:f816:3eff:fef1:1bad'] <3>
apiVIPs: ['192.168.25.199', 'fd2e:6f44:5dd8:c956:f816:3eff:fe78:cf36'] <4>
controlPlanePort: <5>
fixedIPs: <6>
- subnet: <7>
name: subnet-v4
id: subnet-v4-id
- subnet: <7>
name: subnet-v6
id: subnet-v6-id
network: <7>
name: dualstack
id: network-id
----
<1> Dual-stack clusters are supported only with the `TechPreviewNoUpgrade` value.
<2> You must specify an IP address range in the `cidr` field for both IPv4 and IPv6 address families.
<3> Specify the virtual IP (VIP) address endpoints for the Ingress VIP services to provide an interface to the cluster.
<4> Specify the virtual IP (VIP) address endpoints for the API VIP services to provide an interface to the cluster.
<5> Specify the dual-stack network details that are used by all the nodes across the cluster.
<6> The Classless Inter-Domain Routing (CIDR) of any subnet specified in this field must match the CIDRs listed on `networks.machineNetwork`.
<7> You can specify a value for `name`, `id`, or both.
[NOTE]
====
The `ip=dhcp,dhcp6` kernel argument, which is set on all of the nodes, results in a single Network Manager connection profile that is activated on multiple interfaces simultaneously.
Because of this behavior, any additional network has the same connection enforced with an identical UUID. If you need an interface-specific configuration, create a new connection profile for that interface so that the default connection is no longer enforced on it.
====