Loading...

XML

Word

Printable

Epic Name:
AppSets in any namespace
Blocked:
False
Blocked Reason:
None
Ready:
False
Epic Status:
To Do
Hierarchy Progress Bar:

0% To Do, 0% In Progress, 100% Done
Release Note Text:

Hide
With this update, two new fields `.spec. applicationSet.sourceNamespaces` & `.spec. applicationSet.scmProviders` are introduced in ArgoCD CRD to support ApplicationSet in any namespaces. This allows administrators to define a certain set of namespaces where ApplicationSet resources can be managed in. Refer [documentation](#link) for detailed usage.

Show
With this update, two new fields `.spec. applicationSet.sourceNamespaces` & `.spec. applicationSet.scmProviders` are introduced in ArgoCD CRD to support ApplicationSet in any namespaces. This allows administrators to define a certain set of namespaces where ApplicationSet resources can be managed in. Refer [documentation](#link) for detailed usage.
Intelligence Requested:
Market:

Epic Goal

OpenShift GitOps should allow creation of applicationsets outside of control-plane namespaces

Upstream Argo CD already provides support for creation of appsets and sourcing of child apps from non-control plane namespaces. We must provide the ability to leverage this feature within OpenShift GitOps as well.
(https://argo-cd.readthedocs.io/en/stable/operator-manual/applicationset/Appset-Any-Namespace/#overview)

CI - MUST be running successfully with tests automated
Release Technical Enablement - Provide necessary release enablement details and documents.
feature implementation is complete
unit and e2e tests are included

Acceptance criteria are met
Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
User Journey automation is delivered
Support and SRE teams are provided with enough skills to support the feature in production environment

links to

RHSA-2024:127897 Errata Advisory for Red Hat OpenShift GitOps v1.12.0