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

Default Rolebindings Created on OCP 4.16 with No Capabilities

XMLWordPrintable

    • No
    • 0
    • Builds Sprint #5
    • 1
    • Rejected
    • True
    • Hide

      QA is blocked due to no testing cluster available. 
      Raised the cluster-bot bug: https://issues.redhat.com/browse/OCPBUGS-35250

      Show
      QA is blocked due to no testing cluster available.  Raised the cluster-bot bug: https://issues.redhat.com/browse/OCPBUGS-35250
    • Hide
      * Previously, role bindings related to the `ImageRegistry`, `Build`, and `DeploymentConfig` capabilities were created in every namespace, even if the respective capability was disabled. With this release, the role bindings are only created if the respective cluster capability is enabled on the cluster. (link:https://issues.redhat.com/browse/OCPBUGS-34384[*OCPBUGS-34384*])
      Show
      * Previously, role bindings related to the `ImageRegistry`, `Build`, and `DeploymentConfig` capabilities were created in every namespace, even if the respective capability was disabled. With this release, the role bindings are only created if the respective cluster capability is enabled on the cluster. (link: https://issues.redhat.com/browse/OCPBUGS-34384 [* OCPBUGS-34384 *])
    • Bug Fix
    • Done

      This is a clone of issue OCPBUGS-34077. The following is the description of the original issue:
      —
      In OCP 4.16.0, the default role bindings for image puller, image pusher, and deployer are created, even if the respective capabilities are disabled on the cluster.

              adkaplan@redhat.com Adam Kaplan
              openshift-crt-jira-prow OpenShift Prow Bot
              Apoorva Jagtap Apoorva Jagtap
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: