-
Notifications
You must be signed in to change notification settings - Fork 336
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
HOSTEDCP-1960: Add KubeAPIExteralName api #5458
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -432,6 +432,13 @@ type HostedClusterSpec struct { | |
// +required | ||
Platform PlatformSpec `json:"platform"` | ||
|
||
// kubeApiExternalName specifies the external name for the Kube API Server service. | ||
// +kubebuilder:validation:MaxLength=100 | ||
// +kubebuilder:validation:MinLength=1 | ||
// +kubebuilder:example: "api.example.com" | ||
// +optional | ||
KubeAPIExternalName string `json:"kubeApiExternalName,omitempty"` | ||
|
||
// controllerAvailabilityPolicy specifies the availability policy applied to critical control plane components like the Kube API Server. | ||
// Possible values are HighlyAvailable and SingleReplica. The default value is HighlyAvailable. | ||
// +optional | ||
|
@@ -1423,6 +1430,10 @@ type HostedClusterStatus struct { | |
// +optional | ||
KubeConfig *corev1.LocalObjectReference `json:"kubeconfig,omitempty"` | ||
|
||
// CustomKubeConfig specifies the name and key for the External Custom kubeconfig secret | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Let's use lower case by convention for api field docs so gdocs generation result in the serialized version of the field, i.e. "customKubeConfig" Is the underlying business logic tied with the .kubeAPIExternalName? If so let's have cel validation here to capture that. Also we can probably put both fields behind the same struct so we preserve the ability to organically grow this semantic. we use "custom" term here but "external..." above can we consolidate on using a single one all the time. |
||
// +optional | ||
CustomKubeConfig *corev1.LocalObjectReference `json:"customKubeConfig,omitempty"` | ||
|
||
// KubeadminPassword is a reference to the secret that contains the initial | ||
// kubeadmin user password for the guest cluster. | ||
// +optional | ||
|
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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.
kubeApiExternalName -> kubeAPIExternalName
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.
See https://github.com/openshift/hypershift/pull/5458/files#r1930322503
What happens if I set this field? What need to be done out of band?...
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.
Let's use same cel regex validation we do for BaseDomain and others