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

change gitops-operator installation namespace

XMLWordPrintable

    • 3
    • False
    • None
    • False
    • SECFLOWOTL-87 - Operator to handle fleets of ArgoCD CRs
    • Hide
      This enhancement sets the default installation of the operator to its own namespace called "openshift-gitops-operator" as opposed to previously being installed in the "openshift-operators" namespace out of the box. Users are still able to choose "openshift-operators" through a drop down menu available in the OperatorHub UI at installation time if they wish. Users are also able to select the check box to enable cluster monitoring on this namespace, which makes the operator's performance metrics accessible within the OpenShift console. (Note: the operator needs to be installed in any namespace other than "openshift-operators" for metrics to become available in the OpenShift console.
      Show
      This enhancement sets the default installation of the operator to its own namespace called "openshift-gitops-operator" as opposed to previously being installed in the "openshift-operators" namespace out of the box. Users are still able to choose "openshift-operators" through a drop down menu available in the OperatorHub UI at installation time if they wish. Users are also able to select the check box to enable cluster monitoring on this namespace, which makes the operator's performance metrics accessible within the OpenShift console. (Note: the operator needs to be installed in any namespace other than "openshift-operators" for metrics to become available in the OpenShift console.
    • GITOPS Sprint 241, GITOPS Sprint 243, GITOPS Sprint 3244

      Story (Required)

      As a admin of gitops-operator trying to install the operator, I want to be able to install the operator in its own namespace 

      Background (Required)

      OpenShift GitOps operator is currently installed in the "openshift-operators" namespace out of the box, which no choice being given to the user. However, going forward we want to expose the operator's metrics to the openshift-monitoring stack out of the box, which is not possible as long as the operator lives in the "openshfit-operators" namespace, since this namespace is not watched by the monitoring stack

       

      We need to move the operator into its own "openshift-gitops-operator" namespace, and add default cluster monitoring to this namespace in order to make our metrics available within the openshift monitoring dashboard in the console

      Out of scope

      N/A

      Approach (Required)

      • update operator bundle manifests for new namespace and resource naming system
      • add suggested namespace annotation in the CSV which allows users to select the new namespace as the one to install the operator in through OperatorHub UI
      • add cluster-monitoring label annotation to the CSV so the new namespace is watched by the openshift-monitoring stack

      Dependencies

      none

      Acceptance Criteria (Mandatory)

      • Users are presented with the option to install the operator in "openshift-gitops-operator" namespace through OperatorHub UI at installation time
      • Users are presented with the option to enable cluster monitoring at operator installation time

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      • Continuous Delivery pipeline(s) is able to proceed with new code included
      • Customer facing documentation, API docs etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

            jrao@redhat.com Jaideep Rao
            jrao@redhat.com Jaideep Rao
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: