• Can we add a extra bit of code that compares bootstrap-hub-kubeconfig and the hub-kubeconfig-secret for all the managed clusters and maybe display a banner somewhere for managed clusters that the kubeconfig secret is outdated and it needs to be updated?
• I have seen quite a few cases where customers have reported the clusters are in unknown state. There should be an easier way of identifying this issue and remediate as per:

https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html-single/troubleshooting/index#resolving-clusters-offline-after-certificate-change

• This is a product suggestion rather than a customer requirement.