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

Cluster-scoped Rollouts install support

XMLWordPrintable

    • 13
    • False
    • None
    • False
    • SECFLOWOTL-93 - Promote Rollouts to GA
    • Hide
      With this update, OpenShift GitOps now supports both cluster-scoped and namespace-scoped Argo Rollouts installs. An Argo Rollouts install will default to watching all Rollout resources across all namespaces on the cluster. However, the operator configuration can also be modified to instead allow only namespace-scoped Argo Rollouts installs, that is, Rollouts would default to only watching namespaces in which Rollouts is installed.
       
      Breaking change: The scope of a default installation of Argo Rollouts has changed. Previously, an Argo Rollouts installation via OpenShift GitOps would default to namespace-scoped. Argo Rollouts now instead defaults to cluster-scoped. If the original namespace-scoped behaviour is required, see the documentation for how to enable this feature. However, note that on a cluster Argo Rollouts can be installed as EITHER cluster-scoped, OR as namespace-scoped, but not both.
      Show
      With this update, OpenShift GitOps now supports both cluster-scoped and namespace-scoped Argo Rollouts installs. An Argo Rollouts install will default to watching all Rollout resources across all namespaces on the cluster. However, the operator configuration can also be modified to instead allow only namespace-scoped Argo Rollouts installs, that is, Rollouts would default to only watching namespaces in which Rollouts is installed.   Breaking change: The scope of a default installation of Argo Rollouts has changed. Previously, an Argo Rollouts installation via OpenShift GitOps would default to namespace-scoped. Argo Rollouts now instead defaults to cluster-scoped. If the original namespace-scoped behaviour is required, see the documentation for how to enable this feature. However, note that on a cluster Argo Rollouts can be installed as EITHER cluster-scoped, OR as namespace-scoped, but not both.
    • Enhancement
    • Done
    • GITOPS Service EE Sprint 256, GITOPS Service EE Sprint 257, GITOPS Service EE Sprint 258, GITOPS Service EE Sprint 3254, GitOps Scarlet - Sprint 2261

      See https://github.com/argoproj-labs/argo-rollouts-manager/issues/20 for all details.

      Please discuss the issue on GitHub, and not on the JIRA.

      Acceptance Criteria:

      • Because this this involves a change to the API behaviour, we should make sure this is documented by docs within the release notes (for example example, using 'error box styling')

              jparsai Jayendra Parsai
              jgwest Jonathan West
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: