Closed samene closed 2 years ago
This is intentional behaviour. As per this commit -
https://github.com/rancher/rke/commit/217e1b41b8fe0ffc362f75ab7bfd71e644d101f3
rke-tools is dependent on the rke version and not on the kubernetes version. so they have explicitly added code to "replace" the rke-tools image version from the kubernetes version section (which is 1.0.78 for 1.20.14-rancher2-1) with the rke-tools of the "default" kubernetes version that this version of rke supports. In our data.json (which we download in every build) this default version is now 1.24.4-rancher1-1 and so its rke-tools version is fetched which is 1.0.87.
"RKEDefaultK8sVersions": {
"0.3": "v1.16.3-rancher1-1",
"default": "v1.24.4-rancher1-1"
}
RKE version: : 1.3.0
Docker version: (
docker version
,docker info
preferred): 1.20Operating system and kernel: (
cat /etc/os-release
,uname -r
preferred): CentOS 7Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO) Bare metal
cluster.yml file:: using the rke terraform provider. This is the plan
Steps to Reproduce:
Note the version -
kubernetes_version = "v1.20.14-rancher2-1"
in the plan.we are using latest data.json from here - https://releases.rancher.com/kontainer-driver-metadata/dev-v2.6/data.json
As per this file the system images for 1.20.14-rancher2-1 are
But the installer is also needing rke-tools:v0.1.87 which is not in the mapping. This causes our airgapped installation to fail.
Extra info: This image is used for etcd-rolling-updates
docer ps -a| grep rke-tools