-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
📖 Add clusterclass contract changes to v1alpha3-v1alpha4 conversion guide #5366
📖 Add clusterclass contract changes to v1alpha3-v1alpha4 conversion guide #5366
Conversation
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.
I think this should be cherry picked back to the 0.4 docs too.
4e2d5cb
to
82fd238
Compare
82fd238
to
640c8e6
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.
Thanks for this effort!
Overall lgtm, only two nits to provide some more context about/when those changes are required
|
||
`status.version` - is a string representing the minimum Kubernetes version for the control plane machines in the cluster. | ||
|
||
These fields are a requirement for ClusterClass compatibility. |
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.
These fields are a requirement for ClusterClass compatibility. | |
Please note that implementing those field is a requirement for a control plane provider to be used with ClusterClass and managed topologies. |
`machineTemplate` - is a struct containing details of the control plane | ||
machine template. | ||
|
||
This field is a requirement for ClusterClass compatibility. |
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.
This field is a requirement for ClusterClass compatibility. | |
Please note that implementing those field for control plane providers using machines is a requirement for ClusterClass and managed topologies to work consistently across all the providers. |
Signed-off-by: killianmuldoon <[email protected]>
640c8e6
to
bbc8384
Compare
@fabriziopandini @sbueringer updated now. |
/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.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Update docs to include some changes made to the ControlPlane contract to support ClusterClass.
Signed-off-by: killianmuldoon [email protected]
Fixes #5282