Goal

Develop a feature that allows dynamic specification and modification of external DNS names at any point (day-0 or post-deployment), with automatic updates to KubeConfigs and console login commands to reflect these changes, enhancing user flexibility and cluster accessibility.

Why is this important?

This will allow us to

• Replace the user-facing TLS certificate with one from a public CA without breaking control plane functions (i.e. node bootstrap) which are bound to the internal root CA
• Support split-horizon DNS and NAT scenarios
• Ensure a similar UX to standalone control planes where I can use functions such as "Show Login Command" with the correct KubeConfig and DNS configuration

Scenarios

1. Dynamic DNS Configuration: Allow users to specify and modify external DNS names at any time during the cluster lifecycle.
2. 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.
3. Console Login Adjustments: Update the console login command to dynamically use the latest specified external DNS name.

Acceptance Criteria

• Users can specify and modify external DNS names at cluster creation or at any later point.
• The system automatically generates and updates KubeConfigs when changes to external DNS names are made.
• The console login command reflects the latest external DNS names without manual intervention.
• QE - The feature is tested
• DOC - The feature is documented upstream and downstream

Dependencies (internal and external)

1. Need to discuss with Openshift Console how to reflect the new DNS Names in the respective places to make it similar to OCP Standalone

Previous Work (Optional):

1. …

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Technical Enablement <link to Feature Enablement Presentation>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Enhancement merged: <link to meaningful PR or GitHub Issue>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>