Open oskapt opened 4 years ago
This option was added to support listing system-images per version:
cli.StringFlag{
Name: "version",
Usage: "Generate the default system images for specific k8s versions",
},
If there is any documentation stating this can be used to setup the cluster yaml, this needs to be changed asap.
And in the process of fixing this, rke config
needs to be refactored to use the latest best practices, e.g. using kubernetes_version
vs setting system_images
amongst other things that have changed in the past.
I don't know if there's any documentation, but here's the question - if each version of RKE can install three versions of Kubernetes, how do you get it to install anything other than the most recent one? It would seem like you would set this as part of rke config
, and the --version
flag that's available seems like the way you would do it.
@superseb Lab 2 of Rancher Academy actually mentions the use of the rke config --version
for configuring the kube version in part 1a. This should be removed from that lab writeup.
@superseb Lab 2 of Rancher Academy actually mentions the use of the
rke config --version
for configuring the kube version in part 1a. This should be removed from that lab writeup.
I've removed this from Lab 2.
RKE version:
1.0.4
Steps to Reproduce:
Results:
hyperkube:v1.16.6-rancher1
rke config --version
,kubernetes
uses the default version incluster.yml
-- Edit superseb -- This includes refactoring
rke config
to match the current standards:system_images
but usekubernetes_version
kubernetes_version
configurable