-
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
References to Machine spec.kubernetesVersion seems misleading #3257
Comments
@wfernandes: 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. |
/help |
@vincepri: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed 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. |
/kind documentation |
/assign |
/lifecycle active |
What steps did you take and what happened:
In the following files we reference
spec.kubernetesVersion
for the Machine object. But I don't believe we have that property.cluster-api/bootstrap/kubeadm/types/v1beta1/types.go
Line 67 in fd73b18
cluster-api/bootstrap/kubeadm/config/crd/bases/bootstrap.cluster.x-k8s.io_kubeadmconfigs.yaml
Line 285 in fd73b18
cluster-api/bootstrap/kubeadm/config/crd/bases/bootstrap.cluster.x-k8s.io_kubeadmconfigs.yaml
Line 1091 in fd73b18
cluster-api/bootstrap/kubeadm/config/crd/bases/bootstrap.cluster.x-k8s.io_kubeadmconfigtemplates.yaml
Line 306 in fd73b18
cluster-api/bootstrap/kubeadm/config/crd/bases/bootstrap.cluster.x-k8s.io_kubeadmconfigtemplates.yaml
Line 1144 in fd73b18
What did you expect to happen:
I expected it to be
spec.Version
as described here:cluster-api/api/v1alpha3/machine_types.go
Lines 58 to 61 in fd73b18
/kind bug
/area api
The text was updated successfully, but these errors were encountered: