Epic Goal
- Currently sourceNamespaces in the ArgoCD CR supports only valid namespaces and wildcard characters/glob patterns are not supported. Wildcard character support is available in the upstream code base. Providing a similar support in the operator would be beneficial for end users.
Why is this important?
- Customers who have many namespaces (hundreds/thousands) of namespaces to manage, would rather prefer a glob pattern or wild card based specification for the sourceNamespaces field rather than specfiying each namespace explicitly. The upstream ArgoCD supports such wild card/glob pattern based configuration. This would enable end users to specify sourceNamespaces similar to how it is done by upstream ArgoCD implementation.
Scenarios
- ...
Acceptance Criteria (Mandatory)
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions::
- ...
Done Checklist
- 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
- is cloned by
-
GITOPS-3936 Support for negation operator in sourceNamespaces field of ArgoCD CR
-
- Closed
-