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

Details

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

      None

      Show
      None
    • Hide
      Previous versions of OCP did not include cluster name in names of the OpenStack load balancer resources created by OpenStack Cloud Controller Manager. This means that if multiple OCP clusters were running in a single OpenStack project, there were issues when LoadBalancer Services were named the same in these clusters.

      Now the cluster name will be included in the names of the Octavia resources. When upgrading from previous OCP version the load balancers will be renamed. The new names will follow the pattern `kube_service_<cluster-name>_<namespace>_<service-name>` instead of `kube_service_kubernetes_<namespace>_<service-name>`.
      Show
      Previous versions of OCP did not include cluster name in names of the OpenStack load balancer resources created by OpenStack Cloud Controller Manager. This means that if multiple OCP clusters were running in a single OpenStack project, there were issues when LoadBalancer Services were named the same in these clusters. Now the cluster name will be included in the names of the Octavia resources. When upgrading from previous OCP version the load balancers will be renamed. The new names will follow the pattern `kube_service_<cluster-name>_<namespace>_<service-name>` instead of `kube_service_kubernetes_<namespace>_<service-name>`.
    • Bug Fix
    • In Progress

    Description

      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:

       

      Attachments

        Activity

          People

            mdulko Michał Dulko
            mdulko Michał Dulko
            Itshak Brown Itshak Brown
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated: