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

3.10.6. Configuring a cluster with dual-stack networking

You can create a dual-stack cluster on RHOSP. However, the dual-stack configuration is enabled 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
링크 복사

Procedure

  1. Create a network with 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 dualstack network MTU must accommodate both the minimum MTU for IPv6, which is 1280, and the OVN-Kubernetes encapsulation overhead, which is 100.

    참고

    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:
    1 
    
  - 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:
    3 
    
  - 172.30.0.0/16
  - fd02::/112
platform:
  openstack:
    ingressVIPs: ['192.168.25.79', 'fd2e:6f44:5dd8:c956:f816:3eff:fef1:1bad']
    4 
    
    apiVIPs: ['192.168.25.199', 'fd2e:6f44:5dd8:c956:f816:3eff:fe78:cf36']
    5 
    
    controlPlanePort:
    6 
    
      fixedIPs:
    7 
    
      - subnet:
    8 
    
          name: subnet-v4
          id: subnet-v4-id
      - subnet:
    9 
    
          name: subnet-v6
          id: subnet-v6-id
      network:
    10 
    
        name: dualstack
        id: network-id

    1 2 3
    You must specify an IP address range for both the IPv4 and IPv6 address families.
    4
    Specify the virtual IP (VIP) address endpoints for the Ingress VIP services to provide an interface to the cluster.
    5
    Specify the virtual IP (VIP) address endpoints for the API VIP services to provide an interface to the cluster.
    6
    Specify the dual-stack network details that are used by all of the nodes across the cluster.
    7
    The CIDR of any subnet specified in this field must match the CIDRs listed on networks.machineNetwork.
    8 9
    You can specify a value for either name or id, or both.
    10 10
    Specifying the network under the ControlPlanePort field is optional.

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

    You must specify an IP address range for both the IPv4 and IPv6 address families.
    Specify the virtual IP (VIP) address endpoints for the Ingress VIP services to provide an interface to the cluster.
    Specify the virtual IP (VIP) address endpoints for the API VIP services to provide an interface to the cluster.
    Specify the dual-stack network details that are used by all the nodes across the cluster.
    The CIDR of any subnet specified in this field must match the CIDRs listed on networks.machineNetwork.
    You can specify a value for either name or id, or both.
    Specifying the network under the ControlPlanePort field is optional.
참고

When using an installation host in an isolated dual-stack network, the IPv6 address may 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 contains 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 contains 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 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.

Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 소개

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

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

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

Red Hat 문서 정보

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

Legal Notice

Theme

© 2026 Red Hat맨 위로 이동