-
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
Block on unsupported Kubernetes version #4321
Comments
/milestone v0.4.0 |
@fabriziopandini: The label(s) In response to this:
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/test-infra repository. |
Is this a duplicate of #3697 ? |
#3697 is about semantic validation of the version |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/lifecycle frozen @fabriziopandini What are some action items we can take as part of this issue? |
/close |
@fabriziopandini: Closing this issue. In response to this:
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/test-infra repository. |
User Story
As a operator, I would like to get informed about unsupported Kubernetes versions when creating resources.
Detailed Description
As per #4292 (comment)
CABPK currently supports only Kubernetes versions >= v1.13, but the user does not get an error message when creating Machines/MachineDeployments/KubeadmControlPlane with older version
Anything else you would like to add:
This is tricky, because in some cases the kubernetes version could be defined on another resources vs the KubeadmConfig/KubeadmConfigTemplate (e.g. Machines, Machine deployments), and those resurces are generic - should not be bound to CABPK limitations.
/kind feature
The text was updated successfully, but these errors were encountered: