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

Enable/Disable redis and controller workloads

XMLWordPrintable

    • False
    • None
    • False
    • SECFLOWOTL-89 - Support a small footprint GitOps for MicroShift
    • Hide
      With this enhancement users are now able to selectively disable both the `redis` and `application-controller` workloads for a namespace-scoped Argo CD instance.

      In order to disable a workload, add the `enabled: false` flag to the `spec.<component>.enabled` field in the Argo CD CR.

      ```
      spec:
        controller:
          enabled: false
        redis:
          enabled: false
      ```
      When the flag is not set, the default behavior is to be enabled.
      Note: This feature is ONLY available for the redis and application-controller workloads currently. A feature to add this ability to other workloads is planned for an upcoming v1.11 z-stream release.

      Show
      With this enhancement users are now able to selectively disable both the `redis` and `application-controller` workloads for a namespace-scoped Argo CD instance. In order to disable a workload, add the `enabled: false` flag to the `spec.<component>.enabled` field in the Argo CD CR. ``` spec:   controller:     enabled: false   redis:     enabled: false ``` When the flag is not set, the default behavior is to be enabled. Note: This feature is ONLY available for the redis and application-controller workloads currently. A feature to add this ability to other workloads is planned for an upcoming v1.11 z-stream release.

      Story (Required)

      Original story was to enable/disable all workloads but during release candidate testing we ran into issues with some of the workloads. The only ones that work as expected currently are for redis and application controller, so we have decided to call that out as a feature for only those workloads and fix the rest of them in v1.11.1. 

      Background (Required)

      <Describes the context or background related to this story>

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

      <Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

      Dependencies

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

      Acceptance Criteria (Mandatory)

      <Describe edge cases to consider when implementing the story and defining tests>

      <Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

      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

            isequeir@redhat.com Ishita Sequeira
            rescott1 Regina Scott
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: