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

Services collide if there are multiple clusters in a single OpenStack projects

XMLWordPrintable

    • ?
    • Moderate
    • No
    • ShiftStack Sprint 241, ShiftStack Sprint 242, ShiftStack Sprint 244, ShiftStack Sprint 248, ShiftStack Sprint 249, ShiftStack Sprint 250, ShiftStack Sprint 251, ShiftStack Sprint 252, ShiftStack Sprint 253
    • 9
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, {product-title} did not include the cluster name in the names of the {rh-openstack} load balancer resources that were created by the OpenStack Cloud Controller Manager. This behavior caused issues when `LoadBalancer` services had the same name in multiple clusters that ran in a single {rh-openstack} project. Now, the cluster name is included in the names of Octavia resources.
      +
      When upgrading from a previous cluster version, the load balancers are renamed. The new names follow the pattern `kube_service_<cluster-name>_<namespace>_<service-name>` instead of `kube_service_kubernetes_<namespace>_<service-name>`. (link:https://issues.redhat.com/browse/OCPBUGS-13680[*OCPBUGS-13680*])
      Show
      * Previously, {product-title} did not include the cluster name in the names of the {rh-openstack} load balancer resources that were created by the OpenStack Cloud Controller Manager. This behavior caused issues when `LoadBalancer` services had the same name in multiple clusters that ran in a single {rh-openstack} project. Now, the cluster name is included in the names of Octavia resources. + When upgrading from a previous cluster version, the load balancers are renamed. The new names follow the pattern `kube_service_<cluster-name>_<namespace>_<service-name>` instead of `kube_service_kubernetes_<namespace>_<service-name>`. (link: https://issues.redhat.com/browse/OCPBUGS-13680 [* OCPBUGS-13680 *])
    • Bug Fix
    • Done

      Description of problem:

      If two clusters share a single OpenStack projects, cloud-provider-openstack won't distinguish type=LoadBalancer Services between them if they have the same namespace name and service name.
      
      https://github.com/kubernetes/cloud-provider-openstack/issues/2241

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

       

      How reproducible:

      Always

      Steps to Reproduce:

      1. Deploy 2 clusters.
      2. Create LoadBalancer Services of the same name in default namespaces of both clusters.
      

      Actual results:

      cloud-provider-openstack fights over ownership of the LB.

      Expected results:

      LBs are distinguished.

      Additional info:

       

            sfinucan@redhat.com Stephen Finucane
            mdulko Michał Dulko
            Itshak Brown Itshak Brown
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: