-
Notifications
You must be signed in to change notification settings - Fork 1.8k
[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
base: main
Are you sure you want to change the base?
Conversation
e366ae8
to
06237a7
Compare
a81e330
to
41adc52
Compare
41adc52
to
2234f54
Compare
3ea96ea
to
246f1fb
Compare
There was a problem hiding this 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!
246f1fb
to
efcfc8f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/lgtm |
There was a problem hiding this 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!
modules/hcp-custom-kubeapi.adoc
Outdated
|
||
* 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* 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 |
modules/hcp-custom-kubeapi.adoc
Outdated
|
||
* 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* 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 |
modules/hcp-custom-kubeapi.adoc
Outdated
* 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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. |
efcfc8f
to
a45a4a8
Compare
Thanks for the review, @lpettyjo! |
a45a4a8
to
379d108
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
modules/hcp-custom-dns.adoc
Outdated
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. |
There was a problem hiding this comment.
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"?
There was a problem hiding this comment.
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!
/lgtm |
379d108
to
465d90b
Compare
@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. |
/lgtm |
The This is because your PR targets the 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. |
Version(s): 4.19+
Issue: https://issues.redhat.com/browse/OSDOCS-14539
Link to docs preview:
This PR adds one module to several places in the HCP docs:
QE review:
Additional information: This PR should be published for the HCP 4.19 GA on July 2.