Feature Overview

🚀 Enhanced Argo CD Multi-Namespace ApplicationSet Management

This feature is designed to ensure complete compatibility across all Red Hat Advanced Cluster Management (RHACM) deployment patterns: Push, Pull, Agent Mode, and Add-on GitOps deployments.

🎯 Core Feature & Rationale

The enhancement is based on native Argo CD ApplicationSet capabilities, which supports ApplicationSet resources in namespaces outside of the Argo CD control plane.

Key Benefits on the Hub

• Improved Scalability and Organization: Argo CD administrators can designate a specific list of namespaces where ApplicationSet resources can be created, updated, and reconciled.

• Decoupled Application Generation: Since the Applications generated by an ApplicationSet are created in the same namespace as the ApplicationSet itself, this natively supports deploying GitOps Applications in any designated namespace.

• Natural Hub Enhancement: This capability represents the logical next step in improving the organization and tenancy of GitOps resources on the RHACM Hub cluster, solidifying the value of our "Argo CD Plus Model" for advanced deployment scenarios.

🌐 Impact Across RHACM Deployment Models

1. Push Model (Hub-based ApplicationSet)

This model directly benefits from the core enhancement, allowing administrators to organize ApplicationSets across multiple namespaces on the Hub for cleaner, tenant-aware management.

2. Pull Model & Multi-Namespace Deployment

This enhancement directly supports more complex and granular Pull Model deployments by enabling namespace-isolated tenancy on both the Hub and the managed clusters.

Proposed Pull Model Flow:

Result: Each managed cluster will have multiple, isolated Applications deployed (e.g., ns1/app1, ns2/app2, ..., nsN/appN).

Implementation Note: The existing gitops-operator (or relevant add-on) can be leveraged and configured to deploy OpenShift GitOps instances into the corresponding namespaces (ns1, ns2, ..., nsN) on each managed cluster, fulfilling the multi-tenancy requirements.

Goals

Gitops already supports a Technical-preview: GITOPS-3754

• …

Requirements

This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.

(Optional) Use Cases

This Section:

• Main success scenarios - high-level user stories
• Alternate flow/scenarios - high-level user stories
• ...

Questions to answer

• ...

Out of Scope

• …

Background, and strategic fit

This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?

Assumptions

• ...

Customer Considerations

• ...

Documentation Considerations

Questions to be addressed:

• What educational or reference material (docs) is required to support this
  product feature? For users/admins? Other functions (security officers, etc)?
• Does this feature have a doc impact?
• New Content, Updates to existing content, Release Note, or No Doc Impact
• If unsure and no Technical Writer is available, please contact Content
  Strategy.
• What concepts do customers need to understand to be successful in
  [action]?
• How do we expect customers will use the feature? For what purpose(s)?
• What reference material might a customer want/need to complete [action]?
• Is there source material that can be used as reference for the Technical
  Writer in writing the content? If yes, please link if available.
• What is the doc impact (New Content, Updates to existing content, or
  Release Note)?