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

ClusterRole collision with monitoring stack via OLM

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • 4.15
    • 4.14
    • Monitoring
    • None
    • Informational
    • No
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      After creating a operatorgroup called "monitoring", CMO starts complaining apparently.
      See: https://redhat-internal.slack.com/archives/C0VMT03S5/p1686236366355359 for more details.

       

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

       

      How reproducible:

       

      Steps to Reproduce:

      1.
2.
3.

      Actual results:

       

      Expected results:

      Because it's not easy to change the ClusterRole name (see https://redhat-internal.slack.com/archives/C0VMT03S5/p1686243328011009?thread_ts=1686236366.355359&cid=C0VMT03S5), maybe we should have a deny list for names we can set to operatorgroup

creating a operatorgroup called "cluster" e.g. can break other components, see https://redhat-internal.slack.com/archives/C3VS0LV41/p1686153497401719

      Additional info:

      slack thread https://redhat-internal.slack.com/archives/C0VMT03S5/p1686236366355359

            rh-ee-amrini Ayoub Mrini
            rh-ee-amrini Ayoub Mrini
            Junqi Zhao Junqi Zhao
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: