Skip to content

[OSDOCS-14539]: Custom DNS name #94090

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

lahinson
Copy link
Contributor

@lahinson lahinson commented Jun 2, 2025

@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jun 2, 2025
@lahinson lahinson force-pushed the osdocs-14539-hcp-customized-dns branch 2 times, most recently from e366ae8 to 06237a7 Compare June 2, 2025 14:39
@lahinson lahinson closed this Jun 2, 2025
@lahinson lahinson reopened this Jun 2, 2025
@lahinson lahinson force-pushed the osdocs-14539-hcp-customized-dns branch 2 times, most recently from a81e330 to 41adc52 Compare June 2, 2025 17:50
@openshift-ci openshift-ci bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jun 2, 2025
@lahinson lahinson force-pushed the osdocs-14539-hcp-customized-dns branch from 41adc52 to 2234f54 Compare June 2, 2025 17:51
@openshift-ci openshift-ci bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jun 2, 2025
@lahinson lahinson force-pushed the osdocs-14539-hcp-customized-dns branch 3 times, most recently from 3ea96ea to 246f1fb Compare June 2, 2025 20:21
Copy link

@jparrill jparrill left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dropped a comment. Thanks!

@lahinson lahinson force-pushed the osdocs-14539-hcp-customized-dns branch from 246f1fb to efcfc8f Compare June 3, 2025 13:43
Copy link

@jparrill jparrill left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 3, 2025
@lahinson lahinson changed the title [OSDOCS-14539]: Custom KubeAPI name [OSDOCS-14539]: Custom DNS name Jun 3, 2025
@jiezhao16
Copy link

/lgtm

@lahinson lahinson added this to the Continuous Release milestone Jun 3, 2025
@lahinson lahinson added the peer-review-needed Signifies that the peer review team needs to review this PR label Jun 3, 2025
@lpettyjo lpettyjo added peer-review-in-progress Signifies that the peer review team is reviewing this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Jun 3, 2025
@lpettyjo lpettyjo self-requested a review June 3, 2025 19:35
@lpettyjo lpettyjo removed their request for review June 3, 2025 19:36
Copy link
Contributor

@lpettyjo lpettyjo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few small comments. Otherwise, LGTM!


* To replace the user-facing TLS certificate with one from a public CA without breaking the control plane functions that are bound to the internal root CA
* To support split-horizon DNS and NAT scenarios
* To ensure a similar experience to standalone control planes, where you can use functions such as the "Show Login Command" function with the correct `kubeconfig` and DNS configuration
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* To ensure a similar experience to standalone control planes, where you can use functions such as the "Show Login Command" function with the correct `kubeconfig` and DNS configuration
* To ensure a similar experience to standalone control planes, where you can use functions, such as the "Show Login Command" function with the correct `kubeconfig` and DNS configuration


* To replace the user-facing TLS certificate with one from a public CA without breaking the control plane functions that are bound to the internal root CA
* To support split-horizon DNS and NAT scenarios
* To ensure a similar experience to standalone control planes, where you can use functions such as the "Show Login Command" function with the correct `kubeconfig` and DNS configuration
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* To ensure a similar experience to standalone control planes, where you can use functions such as the "Show Login Command" function with the correct `kubeconfig` and DNS configuration
* To ensure a similar experience to standalone control planes, where you can use functions, such as the "Show Login Command" function with the correct `kubeconfig` and DNS configuration

* To support split-horizon DNS and NAT scenarios
* To ensure a similar experience to standalone control planes, where you can use functions such as the "Show Login Command" function with the correct `kubeconfig` and DNS configuration

In order to define a DNS name, you insert a domain name in the `kubeAPIServerDNSName` field of a `HostedCluster` object. You can define the name either during your initial setup or during day-2 operations.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
In order to define a DNS name, you insert a domain name in the `kubeAPIServerDNSName` field of a `HostedCluster` object. You can define the name either during your initial setup or during day-2 operations.
To define a DNS name, insert a domain name in the `kubeAPIServerDNSName` field of a `HostedCluster` object. You can define the name either during your initial setup or during day-2 operations.

@lpettyjo lpettyjo added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Jun 3, 2025
@lahinson lahinson force-pushed the osdocs-14539-hcp-customized-dns branch from efcfc8f to a45a4a8 Compare June 4, 2025 15:00
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jun 4, 2025
@lahinson
Copy link
Contributor Author

lahinson commented Jun 4, 2025

Thanks for the review, @lpettyjo!

@lahinson lahinson force-pushed the osdocs-14539-hcp-customized-dns branch from a45a4a8 to 379d108 Compare June 4, 2025 16:09
Copy link

@jparrill jparrill left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 4, 2025
This process does not directly affect the data plane, so no rollouts are expected to occur. The `HostedControlPlane` namespace receives the changes from the HyperShift Operator and deletes the corresponding fields.
====

If you remove the `kubeAPIServerDNSName` field from the specification, all newly generated secrets and the `CustomKubeconfig` reference are removed from the cluster and from the `status` field.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about replacing "the specification" with " the specification for the HostedCluster object"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good suggestion -- it's better to be clear. I'll make that update. Thanks!

@wewang58
Copy link

wewang58 commented Jun 5, 2025

/lgtm

@lahinson lahinson force-pushed the osdocs-14539-hcp-customized-dns branch from 379d108 to 465d90b Compare June 5, 2025 13:53
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jun 5, 2025
Copy link

openshift-ci bot commented Jun 5, 2025

@lahinson: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@wewang58
Copy link

wewang58 commented Jun 6, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 6, 2025
@bergerhoffer
Copy link
Contributor

The branch/enterprise-4.20 label has been added to this PR.

This is because your PR targets the main branch and is labeled for enterprise-4.19. And any PR going into main must also target the latest version branch (enterprise-4.20).

If the update in your PR does NOT apply to version 4.20 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch/enterprise-4.19 branch/enterprise-4.20 lgtm Indicates that a PR is ready to be merged. ok-to-merge peer-review-done Signifies that the peer review team has reviewed this PR size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants