-
Feature
-
Resolution: Unresolved
-
Major
-
ACM 2.11.3
-
Product / Portfolio Work
-
False
-
-
False
-
Not Selected
-
50% To Do, 50% In Progress, 0% Done
Epic Goal
- update the hub cluster when certificates are changed on the managed cluster
- as the user/owner of a managed cluster I need to be able to update the certs on that cluster without access to the ACM hub and ensure that the cluster does not lose connectivity with the hub
Why is this important?
- this is important when the user of a managed cluster can be expected to make this change without having access to the hub cluster
Scenarios
- here the customer deploys clusters with ACM to their customers, but the end customer can have to change the default certificates in use for their own reasons / security practices.
Acceptance Criteria
- when a deployed managed cluster's ingress/API certificate change happens, it is reflected to the hub cluster without any loss of communication between the two
- depends on
-
ACM-16341 Show ClusterDeployment's Unreachable condition as a warning status of managed cluster in Console UI.
-
- Review
-
-
ACM-16488 Invest on how to implement fully automatic CA update.
-
- In Progress
-
- is blocked by
-
-
- In Progress
-
- is related to
-
OCPSTRAT-1599 Increase OpenShift compatibility with GitOps
-
- New
-
- relates to
-
ACM-17241 Add a new Troubleshooting section: Troubleshooting when CA update happened on the managed cluster side.
-
- Closed
-
