1. Proposed title of this feature request: Persistent Change on cluster API Setup | OSD

2. What is the nature and description of the request?

use case: Persistent Change on cluster API Setup

Cx is aiming in the procedure as mentioned in OCP doc[1] for the OSD environment.

[1] https://docs.openshift.com/container-platform/4.15/security/certificates/api-server.html

at the moment they have we've tried it out as we have another FQDN exposed on our network to reach the API of the OSD Cluster

elaboration:

The Hive Components is reverting cx change and they are not able to apply it permanently. (only adding new name not replacing the existing ones.
```
apiVersion: config.openshift.io/v1
kind: APIServer
metadata:
name: cluster
....

names:
<specific_hostname>
servingCertificate:
name: paas-api-cert
```
To achieve this they have tried to actually apply the change from their side by using a service-account

Result: The problem is that the change made by us is getting reverted.

3. Why does the customer need this? (List the business requirements here):

CLI Authentication always needs insecure skip tls verify when calling on non-matching hostname