Uploaded image for project: 'OpenShift Builds'
  1. OpenShift Builds
  2. BUILD-1148

Enable cluster monitoring on openshift-builds namespace during operator installation

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • builds-1.1
    • builds-operator
    • None
    • False
    • None
    • False
    • Customer Facing

      Story (Required)

      As a cluster-admin trying to install Build for OpenShift operator I want cluster-monitoring to be enabled on openshift-builds namespace.

      <Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>

      Background (Required)

      Currently OLM does not ask for cluster-monitoring enablement on the new openshift-builds to be created. If we install the operator out-of-the-box following the GUI or CLI method, the cluster admin need to configure this manually.

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

      GUI installation: Provide the checkbox to enable cluster-monitoring, when selecting the namespace to be created for operator installation

      CLI installation: set the cluster-monitoring label

       

      apiVersion: v1
      kind: Namespace
      metadata:
        labels:
          openshift.io/cluster-monitoring: "true"
        name: openshift-builds 

       

       

      Dependencies

      <Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

      Acceptance Criteria (Mandatory)

      GUI installation: the label openshift.io/cluster-monitoring has been automatically set on openshift-builds namespace

      CLI installation: the documentation is updated with the code example provided in Approach section above.

      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

              Unassigned Unassigned
              laurent.tourreau Laurent TOURREAU
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: