Background:

The current hosted cluster setup allows the addition of DNS names pointing to the API endpoint. However, operational limitations exist, including the automatic generation of KubeConfigs and the static nature of the DNS names used in the console login command. There is a need to enhance flexibility in how DNS names are managed and utilized.

User Story:

As a self-managed HCP cluster service consumer, after changing the external DNS Names on a HostedCluster the differents kubeconfigs should be updated properly.

Automated KubeConfig Updates: Automatically generate and update KubeConfigs to reflect the current external DNS settings, ensuring that users have immediate access to the cluster with the latest configurations.

Acceptance Criteria:

Description of criteria:

• Upstream documentation
• After an update of a External DNS names of a HC, the different Kubeconfigs should be updated with the right TLS certificates.

Engineering Details:

• OCPSTRAT: https://issues.redhat.com/browse/OCPSTRAT-1516