-
Notifications
You must be signed in to change notification settings - Fork 1.4k
🌱 Align ClusterClass ControlPlane with the rest of the fields #5000
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
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 |
|---|---|---|
|
|
@@ -44,7 +44,7 @@ type ClusterClassSpec struct { | |
|
|
||
| // ControlPlane is a reference to a local struct that holds the details | ||
| // for provisioning the Control Plane for the Cluster. | ||
| ControlPlane LocalObjectTemplate `json:"controlPlane,omitempty"` | ||
| ControlPlane ControlPlaneClass `json:"controlPlane,omitempty"` | ||
|
|
||
| // Workers describes the worker nodes for the cluster. | ||
| // It is a collection of node types which can be used to create | ||
|
|
@@ -53,6 +53,23 @@ type ClusterClassSpec struct { | |
| Workers WorkersClass `json:"workers,omitempty"` | ||
| } | ||
|
|
||
| // ControlPlaneClass defines the class for the control plane. | ||
| type ControlPlaneClass struct { | ||
| Metadata ObjectMeta `json:"metadata,omitempty"` | ||
|
|
||
| // LocalObjectTemplate contains the reference to the control plane provider. | ||
| LocalObjectTemplate `json:",inline"` | ||
|
Contributor
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. I am probably missing something but the This ControlPlaneTemplate will internally refer to a machine infrastructure, isnt it?
Member
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. Imho both will reference the same InfrastructureMachineTemplate. This PR makes it explicit on the ClusterClass (i.e. you have to set the ref on the ClusterClass and inside the ControlPlaneTemplate)
Member
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. Exactly, we are making this explicit;
Member
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. Good that fits for my PR as I assume that the ref can be unset in the ControlPlane even if it is set in the ClusterClass.
Contributor
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.
Good to know that we are doing this, however the |
||
|
|
||
| // MachineTemplate defines the metadata and infrastructure information | ||
| // for control plane machines. | ||
| // | ||
| // This field is supported if and only if the control plane provider template | ||
| // referenced above is Machine based and supports setting replicas. | ||
| // | ||
| // +optional | ||
| MachineInfrastructure *LocalObjectTemplate `json:"machineInfrastructure,omitempty"` | ||
| } | ||
|
|
||
| // WorkersClass is a collection of deployment classes. | ||
| type WorkersClass struct { | ||
| // MachineDeployments is a list of machine deployment classes that can be used to create | ||
|
|
||
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Uh oh!
There was an error while loading. Please reload this page.