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

Too many RoleBinding on namespaces managed by GitOps

XMLWordPrintable

    • 8
    • False
    • False
    • Hide
      Before this update, while creating a namespace with the `managed-by` label it created a lot of `RoleBinding` resources on the new namespace. This update fixes the issue and now {gitops-title} removes the irrelevant `Role` and `RoleBinding` resources created by the previous versions.
      Show
      Before this update, while creating a namespace with the `managed-by` label it created a lot of `RoleBinding` resources on the new namespace. This update fixes the issue and now {gitops-title} removes the irrelevant `Role` and `RoleBinding` resources created by the previous versions.
    • GITOPS Sprint 214

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

      ~~~

      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 | grep gitops
      openshift-gitops-argocd-application-controller Role/openshift-gitops-argocd-application-controller 23h
      openshift-gitops-argocd-dex-server Role/openshift-gitops-argocd-dex-server 23h
      openshift-gitops-argocd-redis-ha Role/openshift-gitops-argocd-redis-ha 23h
      openshift-gitops-argocd-server Role/openshift-gitops-argocd-server 23

      ~~~

      Per our conversation, should be enough with "openshift-gitops-argocd-application-controller"

            yicai@redhat.com Yi Cai
            rhn-support-npaez Nelson Paez
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: