-
Feature
-
Resolution: Unresolved
-
Major
-
None
-
None
-
False
-
-
False
-
Not Selected
Feature Overview
This feature implements the "Multicluster Uplift" for the GitOps plugin. It transitions the current single-cluster Application list into a multicluster-aware dashboard when the plugin is running on an ACM (Advanced Cluster Management) Hub. This allows users to view and manage Argo CD applications across the entire fleet without switching contexts, while maintaining a seamless fallback for standalone OpenShift environments.
Goals
- Centralized Visibility: Provide a "Single Pane of Glass" for Argo CD applications across multiple managed clusters.
- Operational Efficiency: Reduce the "MTTR" (Mean Time to Resolution) by allowing admins to identify and drill down into remote application failures from the Hub.
- Contextual Fluidity: Ensure users can navigate from an application to its specific cluster management page or namespace with one click.
Requirements
| Requirement | Notes | Is MVP? |
| Backend Switching | Detect ACM; use ACM Search as data provider. Fallback to local K8s API if ACM is absent. | YES |
| SDK Integration | Import/initialize @multicluster-sdk/console to handle cross-cluster communication. | YES |
| Multicluster Table | Add Cluster and Namespace columns. Implement filtering by Cluster Name. | YES |
| Live Remote Data | Use useRemoteAPI hook to fetch real-time resource status from managed clusters. | YES |
| Scalability | Support 500+ applications across 50+ clusters without UI lag. | YES |
| CI Automation | MUST be running successfully with test automation (standard for all features). | YES |
| Release Enablement | Provide necessary technical enablement details and documentation. | YES |
(Optional) Use Cases
Main Success Scenarios
- Fleet-wide Monitoring: An admin logs into the Hub and sees a unified list of 200 Argo CD apps spanning 10 clusters, instantly identifying which apps are "Out of Sync."
- Remote Troubleshooting: An admin clicks an application hosted on "Cluster-B," and the details view successfully populates live data fetched via the SDK proxy.
Alternate Flow/Scenarios
- Standalone Mode: A user installs the plugin on a standard OpenShift cluster without ACM. The plugin detects the lack of ACM and displays only the local applications.
- RBAC Denial: A user attempts to view an app on a cluster they don't have permissions for; the SDK returns a 403, and the UI displays a "Permission Denied" state for that specific resource.
Background and Strategic Fit
Context for Developers/Testers: The GitOps plugin was originally built for a "local-only" view. This uplift moves the "Source of Truth" from the local API to the ACM Search API when running on a Hub. Developers must ensure the plugin remains decoupled; it should not break if the ACM operator is missing (dynamic discovery). The @multicluster-sdk/console acts as the mediator to handle the complexity of token passing and proxying requests to remote managed clusters.
Assumptions
- The ACM Search API is healthy and indexed for the GitOps resources.
- Users have the necessary RBAC permissions on managed clusters to view Argo CD resources if they expect to see them on the Hub.
- The @multicluster-sdk/console is compatible with the current plugin version.
Documentation Considerations
- Impact: New Content & Updates to existing content.
- Concepts to Understand: Users must understand the Hub vs. Managed Cluster relationship and how ACM Search aggregates data.
- Purpose: Customers will use this to manage large-scale deployments without manual context-switching between OpenShift consoles.
- Reference Material: * API documentation for the @multicluster-sdk/console.
-
- ACM Search documentation for resource indexing.
- Doc Impact: Updates to existing content (Argo CD plugin guide) and Release Notes regarding multicluster support.
- is related to
-
-
- New
-
