Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-3156

Grafana and Redis RoleBinding on namespaces managed by GitOps

    XMLWordPrintable

Details

    • 8
    • False
    • False

    Description

      When creating a namespace with the manage-by label it creates a lot of RoleBinding on the new namespace:

       

      GitOps version

      [~]$ oc get csv
NAME                               DISPLAY                    VERSION   REPLACES                           PHASE
openshift-gitops-operator.v1.8.3   Red Hat OpenShift GitOps   1.8.3     openshift-gitops-operator.v1.8.2   Succeeded

       

      The namespace I created:

      apiVersion: v1
kind: Namespace
metadata:
   name: test
   labels:
     argocd.argoproj.io/managed-by: openshift-gitops

      The RoleBinding are the following:

      [~]$ oc get rolebindings -n test
NAME                                             ROLE                                                  AGE
openshift-gitops-argocd-application-controller   Role/openshift-gitops-argocd-application-controller   5s
openshift-gitops-argocd-grafana                  Role/openshift-gitops-argocd-grafana                  5s
openshift-gitops-argocd-redis                    Role/openshift-gitops-argocd-redis                    5s
openshift-gitops-argocd-server                   Role/openshift-gitops-argocd-server                   5s
system:deployers                                 ClusterRole/system:deployer                           5s
system:image-builders                            ClusterRole/system:image-builder                      5s
system:image-pullers                             ClusterRole/system:image-puller                       5s

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. GITOPS-1550 Too many RoleBinding on namespaces managed by GitOps

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Activity

            People

              jrao@redhat.com Jaideep Rao
              selrahal@redhat.com Sal Elrahal
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: