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

GitOps Operator enables RHSSO on the default instance

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • 1.2
    • None
    • Operator
    • None
    • 5
    • False
    • False
    • RHDP-320 - Integrated CI/CD experience with OpenShift platform
    • Undefined
    • GITOPS Sprint 202

      As a user, I want to install GitOps Operator on OCP for the first time and the default Argo CD instance should automatically install/enable RHSSO.   However, I do not want RHSSO to be automatically installed to the existing default instance if I upgrade GitOps Operator.   In that case, I can enable SSO on the default Argo CD instance after upgrading GitOps Operator by setting the SSO flag in the ArgoCD CR.

       

      Acceptance Criteria

      • After installing GitOps Operator the first time (i.e. not upgrading), RHSSO ins automatically enabled on the default Arigo CD instance
      • After upgrading GitOps Operator, the default ArgoCd instance should not be enabled with SSO automatically.
      • After upgrading GitOps Operator, I can enable RHSSO on the default ArgoCD instance by setting the SSO flag in the ArgoCD CR.
      • Add unit tests.

              aveerama@redhat.com Abhishek Veeramalla
              wtam_at_redhat William Tam
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: