Red Hat Summit Red Hat Summit지원콘솔개발자평가판 시작연락처

3.10.6. Configuring a cluster with dual-stack networking

Deploy a cluster with both IPv4 and IPv6 addressing on Red Hat OpenStack Platform (RHOSP). From RHOSP 17.1, you can use single-stack IPv6 infrastructure while the cluster provides internal IPv4 connectivity.

You can create a dual-stack cluster on RHOSP.

For RHOSP 17.1, you can deploy a dual-stack OpenShift Container Platform cluster on a single-stack IPv6 RHOSP infrastructure. The OpenShift Container Platform cluster offers IPv4 connectivity internally, even when the underlying RHOSP network only has IPv6 subnets.

For earlier versions of RHOSP, you can enable the dual-stack configuration only if you are using an RHOSP network with IPv4 and IPv6 subnets.

참고

RHOSP does not support the conversion of an IPv4 single-stack cluster to a dual-stack cluster network.

3.10.6.1. Deploying the dual-stack cluster
링크 복사

Create dual-stack networks and VIPs, then edit the install-config.yaml file to deploy an cluster with both IPv4 and IPv6 addressing on Red Hat OpenStack Platform (RHOSP).

Procedure

  1. Create a network with the required subnets:

    • For RHOSP 17.1, you can create a network with an IPv6 subnet. The OpenShift Container Platform cluster offers IPv4 connectivity internally. In the install-config.yaml file, you specify both IPv4 and IPv6 subnets in the controlPlanePort.fixedIPs section.

    • For earlier versions of RHOSP, create a network with both IPv4 and IPv6 subnets.

      The available address modes for the ipv6-ra-mode and ipv6-address-mode fields are: dhcpv6-stateful, dhcpv6-stateless, and slaac.

      참고

      The dual-stack network MTU must accommodate both the minimum MTU for IPv6, which is 1280, and the OVN-Kubernetes encapsulation requirement, which is 100 bytes.

      참고

      DHCP must be enabled on the subnets.

  2. Create the API and Ingress VIPs ports.
  3. 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.

  4. 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:

    Example install-config.yaml

    apiVersion: v1
baseDomain: mydomain.test
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:
  - cidr: "192.168.25.0/24"
  - cidr: "fd2e:6f44:5dd8:c956::/64"
  clusterNetwork:
  - cidr: 10.128.0.0/14
    hostPrefix: 23
  - cidr: fd01::/48
    hostPrefix: 64
  serviceNetwork:
  - 172.30.0.0/16
  - fd02::/112
platform:
  openstack:
    ingressVIPs: ['192.168.25.79', 'fd2e:6f44:5dd8:c956:f816:3eff:fef1:1bad']
    apiVIPs: ['192.168.25.199', 'fd2e:6f44:5dd8:c956:f816:3eff:fe78:cf36']
    controlPlanePort:
      fixedIPs:
      - subnet:
          name: subnet-v4
          id: subnet-v4-id
      - subnet:
          name: subnet-v6
          id: subnet-v6-id
      network:
        name: dualstack
        id: network-id

    • networking.machineNetwork, networking.clusterNetwork, and networking.serviceNetwork specify IP address ranges for both the IPv4 and IPv6 address families. For RHOSP 17.1 deployments on single-stack IPv6 infrastructure, the OpenShift Container Platform cluster offers IPv4 connectivity internally.
    • platform.openstack.ingressVIPs specifies the virtual IP (VIP) address endpoints for the Ingress VIP services to give an interface to the cluster.
    • platform.openstack.apiVIPs specifies the virtual IP (VIP) address endpoints for the API VIP services to give an interface to the cluster.
    • platform.openstack.controlPlanePort specifies the dual-stack network details that all the nodes across the cluster use.
    • platform.openstack.controlPlanePort.fixedIPs specifies the subnets for the control plane port. The CIDR of any subnet specified in this field must match the CIDRs listed on networking.machineNetwork.
    • platform.openstack.controlPlanePort.fixedIPs[].subnet specifies each subnet. You can specify a value for either name or id, or both.

    • platform.openstack.controlPlanePort.network specifies the network. Specifying the network under the controlPlanePort field is optional.

      참고

      For RHOSP 17.1 deployments on single-stack IPv6 infrastructure, you can deploy a dual-stack OpenShift Container Platform cluster. In the install-config.yaml file, specify both IPv4 and IPv6 address ranges for the cluster and service networks. The OpenShift Container Platform cluster offers IPv4 connectivity internally, even though the underlying RHOSP network only has IPv6 subnets. In the controlPlanePort.fixedIPs section, specify both the IPv4 and IPv6 subnets.

      Alternatively, if you want an IPv6 primary dual-stack cluster, edit the install-config.yaml file following the example below:

      Example install-config.yaml

      apiVersion: v1
baseDomain: mydomain.test
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:
  - cidr: "fd2e:6f44:5dd8:c956::/64"
  - cidr: "192.168.25.0/24"
  clusterNetwork:
  - cidr: fd01::/48
    hostPrefix: 64
  - cidr: 10.128.0.0/14
    hostPrefix: 23
  serviceNetwork:
  - fd02::/112
  - 172.30.0.0/16
platform:
  openstack:
    ingressVIPs: ['fd2e:6f44:5dd8:c956:f816:3eff:fef1:1bad', '192.168.25.79']
    apiVIPs: ['fd2e:6f44:5dd8:c956:f816:3eff:fe78:cf36', '192.168.25.199']
    controlPlanePort:
      fixedIPs:
      - subnet:
          name: subnet-v6
          id: subnet-v6-id
      - subnet:
          name: subnet-v4
          id: subnet-v4-id
      network:
        name: dualstack
        id: network-id

    • networking.machineNetwork, networking.clusterNetwork, and networking.serviceNetwork specify IP address ranges for both the IPv4 and IPv6 address families. For RHOSP 17.1 deployments on single-stack IPv6 infrastructure, the OpenShift Container Platform cluster offers IPv4 connectivity internally.
    • platform.openstack.ingressVIPs specifies the virtual IP (VIP) address endpoints for the Ingress VIP services to give an interface to the cluster.
    • platform.openstack.apiVIPs specifies the virtual IP (VIP) address endpoints for the API VIP services to give an interface to the cluster.
    • platform.openstack.controlPlanePort specifies the dual-stack network details that all the nodes across the cluster use.
    • platform.openstack.controlPlanePort.fixedIPs specifies the subnets for the control plane port. The CIDR of any subnet specified in this field must match the CIDRs listed on networking.machineNetwork.
    • platform.openstack.controlPlanePort.fixedIPs[].subnet specifies each subnet. You can specify a value for either name or id, or both.
    • platform.openstack.controlPlanePort.network specifies the network. Specifying the network under the controlPlanePort field is optional.
참고

When using an installation host in an isolated dual-stack network, the IPv6 address might not be reassigned correctly upon reboot.

To resolve this problem on Red Hat Enterprise Linux (RHEL) 8, create a file called /etc/NetworkManager/system-connections/required-rhel8-ipv6.conf that has the following configuration: 

[connection]
type=ethernet
[ipv6]
addr-gen-mode=eui64
method=auto

To resolve this problem on RHEL 9, create a file called /etc/NetworkManager/conf.d/required-rhel9-ipv6.conf that has the following configuration: 

[connection]
ipv6.addr-gen-mode=0

After you create and edit the file, reboot the installation host.

참고

The ip=dhcp,dhcp6 kernel argument, which is set on all of the nodes, results in a single Network Manager connection profile that activates on many interfaces simultaneously. Because of this behavior, any additional network has the same connection enforced with the same 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.

Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

Legal Notice

Theme

© 2026 Red Hat맨 위로 이동