Description of problem:

as discussed on slack
The documentation https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.6/html-single/governance/index#replace-the-bring-your-own-byo-ingress-certificate presents what needs to be done to change an ingress certificate, but in the case of case 03411110 the CA authority is also changing. As raised in the same slack thread that would mean reimporting the clusters would be needed, but the customer cannot because it would break their backups, done through AODP.

Version-Release number of selected component (if applicable):

2.6

How reproducible:

not reproduced in house

Steps to Reproduce:

1. deploy ACM
2. attach a few clusters
3. change the ingress certificate to a certificate by a different authority

Actual results:

Expected results:

Additional info:

this is really a situation where the customer does not want to reimport the clusters if the certificate update is a problem and wants a different method to bring the clusters back if the scenario of https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.6/html-single/troubleshooting/index#troubleshooting-imported-clusters-offline-after-certificate-change as reimporting is not something that can be done.