Uploaded image for project: 'Cluster Observability Operator'
  1. Cluster Observability Operator
  2. COO-1268

clusterrolebindings will affect each other if monitroingstack in different ns have same name

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 1.3.0 RC
    • monitoring-stack
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • None
    • None
    • None
    • None
    • None
    • None

      Install COO with latest upstream image install_coo_upsgream.sh

      Create monitoringstack with same name and in different namespaces
      cluster-role-testing.yml

      expected 

       

      % oc get clusterrolebindings -o json | jq -r '.items[] | select(.subjects[]? | select(.kind=="ServiceAccount" and .name=="multi-ns-prometheus" and .namespace=="e2e-tests")) | .metadata.name' 



% oc get clusterrolebindings -o json | jq -r '.items[] | select(.subjects[]? | select(.kind=="ServiceAccount" and .name=="multi-ns-prometheus" and .namespace=="e2e-tests1")) | .metadata.name' 
multi-ns-prometheus

       
      Sometimes can't get clusterrolebindings for the second command

       

      The root cause is 'ClusterRoleBinding objects with the same name, which bind the same ClusterRole to different ServiceAccounts'

        1. cluster-role-testing.yml
          2 kB
        2. install_coo_upsgream.sh
          1 kB

              jfajersk@redhat.com Jan Fajerski
              hongyli@redhat.com Hongyan Li
              None
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: