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

[cee.neXT] The option of "AUTO-CREATE NAMESPACE" is not working as expected.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Blocker Blocker
    • None
    • None
    • Operator
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Steps to Reproduce:

      • Deploy any app using Argo-CD and select the option of "AUTO-CREATE NAMESPACE"
      • Ideally, the app should be deployed and the namespace should be created but due to this bug it doesn't work
      Show
      Steps to Reproduce: Deploy any app using Argo-CD and select the option of "AUTO-CREATE NAMESPACE" Ideally, the app should be deployed and the namespace should be created but due to this bug it doesn't work

      Issue:

      • "Forbidden" errors are occurring and preventing the serviceaccount from accessing the designated namespace.
      • This issue is hindering the ability of users to utilize the automatic namespace creation and application deployment functionalities of Argo CD.
      • The option of "AUTO-CREATE NAMESPACE" is not working as expected.

      Findings: 

      • When the "auto-create namespace" option is selected, it is anticipated that the task will be completed without issue.
      • The application deployment process by the GitOps operator is dependent on the successful label of the namespace.

              rh-ee-sghadi Siddhesh Ghadi
              rhn-support-bbabbar Bharat Babbar
              Votes:
              1 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: