Uploaded image for project: 'On Prem Networking'
  1. On Prem Networking
  2. OPNET-1

Support dual ipv4 and ipv6 ingress and api VIPs

XMLWordPrintable

    • Dual stack VIPs
    • False
    • False
    • Green
    • Done
    • Impediment
    • 7% To Do, 0% In Progress, 93% Done
    • Hide
      [id="ocp-4-12-nw-api-ingress-ipv6-support"]
      ==== Support for IPv6 virtual IP (VIP) addresses for the Ingress VIP and API VIP services

      With this update, in installer-provisioned infrastructure (IPI) clusters, the `ingressVIP` and `apiVIP` configuration settings in the `install-config.yaml` file are deprecated. Instead, use the `ingressVIPs` and `apiVIPs` configuration settings. These settings support dual-stack networking for applications that require IPv4 and IPv6 access to the cluster by using the Ingress VIP and API VIP services. The `ingressVIPs` and `apiVIPs` configuration settings use a list format to specify an IPv4 address, an IPv6 address or both IP address formats. The order of the list indicates the primary and secondary VIP address for each service. The primary IP address must be from the IPv4 network when using dual stack networking.
      Show
      [id="ocp-4-12-nw-api-ingress-ipv6-support"] ==== Support for IPv6 virtual IP (VIP) addresses for the Ingress VIP and API VIP services With this update, in installer-provisioned infrastructure (IPI) clusters, the `ingressVIP` and `apiVIP` configuration settings in the `install-config.yaml` file are deprecated. Instead, use the `ingressVIPs` and `apiVIPs` configuration settings. These settings support dual-stack networking for applications that require IPv4 and IPv6 access to the cluster by using the Ingress VIP and API VIP services. The `ingressVIPs` and `apiVIPs` configuration settings use a list format to specify an IPv4 address, an IPv6 address or both IP address formats. The order of the list indicates the primary and secondary VIP address for each service. The primary IP address must be from the IPv4 network when using dual stack networking.
    • Feature
    • L
    • Done

      Currently in dual stack we set the VIPs to be either v4 or v6. It is not possible to have both v4 and v6 VIPs at the same time.

      We now have dual stack deployments where there may be both single stack v4 and single stack v6 applications that need to interact with the cluster, so there needs to be a VIP accessible to both of them. This will require adding support for a second VIP to the on-prem loadbalancer.

      For clarity, this work needs to include both ingress and api VIPS. It is also primarily targeted at the baremetal platform, but it will be implemented for all on-prem platforms (baremetal, vsphere, openstack, ovirt) in the interest of not maintaining multiple separate configurations for different platforms. This way if/when other on-prem platforms are looking to do dual stack deployments this part of the process will be ready.

          1.
          		 Docs Tracker Sub-task Closed Undefined Ronan Hennessy
          2.
          		 QE Tracker Sub-task Closed Undefined Zhanqi Zhao
          3.
          		 TE Tracker Sub-task Closed Undefined Chris Fields

              bnemec@redhat.com Benjamin Nemec
              bnemec@redhat.com Benjamin Nemec
              Zhanqi Zhao Zhanqi Zhao
              Votes:
              7 Vote for this issue
              Watchers:
              52 Start watching this issue

                Created:
                Updated:
                Resolved: