Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-30865

LoadBalancer configuration in dualstack should not use subnet-id

XMLWordPrintable

    • ?
    • Low
    • No
    • 1
    • OSDOCS Sprint 250
    • 1
    • Proposed
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      Description of problem:

      When creating a service with type LoadBalancer like the following
      
      apiVersion: v1
      kind: Service
      metadata:
        name: demo-loadbalancer
        namespace: demo
      spec:
        ipFamilies:
        - IPv6
        - IPv4
        ipFamilyPolicy: PreferDualStack
        ports:
        - port: 80
          protocol: TCP
          targetPort: 8080
        selector:
          app: demo
        type: LoadBalancer
      
      While having subnet-id of IPv4 subnet in the LoadBalancer section of cloud-provider-config cm the service is stuck in Pending.
      In this scenario a subnet-id shouldn't be used.
      
      https://docs.openshift.com/container-platform/4.15/installing/installing_openstack/installing-openstack-cloud-config-reference.html should be updated
      
      

      Version-Release number of selected component (if applicable):

      4.15.0-0.nightly-2024-03-09-040926

      How reproducible:

          

      Steps to Reproduce:

          1.
          2.
          3.
          

      Actual results:

          

      Expected results:

          

      Additional info:

          

            mbridges@redhat.com Max Bridges
            itbrown@redhat.com Itshak Brown
            Jon Uriarte Jon Uriarte
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: