rancher / quickstart

381 stars 336 forks source link

Vagrant quickstart kubernetes version cannot be empty #53

Closed Oats87 closed 2 years ago

Oats87 commented 4 years ago

If the vagrant quickstart Kubernetes version is left empty, you end up with errors like:

2020/01/14 03:37:17 [ERROR] getSvcOptions: error finding system image for  resource name may not be empty
2020/01/14 03:37:17 [ERROR] getK8sServiceOptions: k8sVersion  [resource name may not be empty]

This is solved by editing/saving the cluster (you don't have to change anything). Likely a change due to the KDM integration for 2.3+

bashofmann commented 2 years ago

Closing, since the vagrant config contains a default Kubernetes version now.