-
Feature
-
Resolution: Unresolved
-
Major
-
ACM 2.9.3
-
False
-
-
False
-
Not Selected
Feature Overview
At current, after Installing a custom apiserver certificate, clusters that were imported before the customer changed the certificate information are in offline status.
Customer has to refer to our guide to delete the managed cluster import secret on the hub cluster and reimport it.
- https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.9/html-single/troubleshooting/index#troubleshooting-imported-clusters-offline-after-certificate-change
Goals
Customer expect ACM to update the certificate information on the managed-clusters by itself instead of deleting the managed cluster import secret on the hub cluster and reimport it manually.
- is related to
-
ACM-26542 Provide clarity and instruction on how to manage kube-apiserver certificate changes on OCP running an RHACM hub
-
- In Progress
-
- relates to
-
ACM-11001 [RFE] Add a feature to compare the bootstrap-hub-kubeconfig and the hub-kubeconfig-secret for the managed clusters and indicate to the user that the kubeconfig secret is outdated
-
- New
-
-
OCPSTRAT-2568 Enhanced Platform Certificate Lifecycle Management and Compliance
-
- In Progress
-
-
ACM-16488 Invest on how to implement fully automatic CA update.
-
- In Progress
-