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, we need consistency between how HCP and OCP is dealing with the KAS external and internal addresses. Right now the HC KAS does not have the capability to have that distinction.

Acceptance Criteria:

Description of criteria:

• Upstream documentation
• Make sure the KAS are exposed via api and api-int with 2 different addresses

Engineering Details:

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