-
Story
-
Resolution: Done
-
Critical
-
None
Integrate the frontend changes from the multicluster POC, stories CONSOLE-2748 and CONSOLE-2767. The console should function as before if ACM is not installed. The cluster list should only become active when the backend is configured for multicluster. We should align the cluster picker with the latest designs.
This depends on CONSOLE-2832.
We should fix the known issues around access reviews and user settings.
Acceptance Criteria
- User settings are always read and set from the hub cluster rather than the spokes. The console service account only has authority to write the config map to the hub cluster.
- The cluster name is included in the cache key for self subject access reviews. There is a known bug in the POC where you can use an incorrect cached value after switching clusters that must be fixed.
- The code from the POC is cleaned up and merged, but inert if ACM is not installed.
- ACM is removed from the perspective switcher. The "All clusters" item in the cluster picker redirects to ACM.
- is blocked by
-
CONSOLE-2832 Integrate multicluster POC backend changes
- Closed
- is related to
-
PD-929 Finalize cluster context switcher design
- Closed
- links to
1.
|
Fix: Requests for user settings config maps must always go to the hub cluster | Closed | Unassigned | ||
2.
|
Fix: Include cluster name in cache key for access reviews | Closed | Samuel Padgett | ||
3.
|
Fix: Remove resources not on spoke clusters from Redux after API discovery | Closed | Unassigned | ||
4.
|
Create script for running bridge with multi-cluster in a dev environment | Closed | Unassigned |