Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-6330

Allow ARO to enable setting V4InternalSubnets during install process to avoid network CIDR conflict

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • openshift-4.12, openshift-4.16
    • Installer
    • False
    • None
    • False
    • Not Selected

      1. Proposed title of this feature request

      Allow ARO to enable setting V4InternalSubnets during install process to avoid network CIDR conflict.

      2. What is the nature and description of the request?

      The default CNI is OVNKubernetes for 4.11 and above.  OVN-K uses some default CIDR ranges for `InternalTransitSwitchSubnet` and `internalJoinSubnet`.  OVN-Kubernetes reserves these IP address ranges. These subnets cannot be overlapped with any other internal or external network. Therefore this request is to allow customization of these ranges upon ARO cluster install.

      https://docs.openshift.com/container-platform/4.16/rest_api/operator_apis/network-operator-openshift-io-v1.html#spec-defaultnetwork-ovnkubernetesconfig-ipv4

      It is able to be configured after cluster install: https://docs.openshift.com/container-platform/4.16/networking/ovn_kubernetes_network_provider/configure-ovn-kubernetes-subnets.html

      In OCP one can configure the values at install time.

       

      3. Why does the customer need this? (List the business requirements here)

      Customers may have overlap with the defaults on their network.

       

      4. List any affected packages or components.

      OVN-Kubernetes

              mak.redhat.com Marcos Entenza Garcia
              okashi1@redhat.com Oren Kashi
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: