When RKE is deploying Kubernetes, there are several images that are pulled. These images are used as Kubernetes system components as well as helping to deploy these system components.
v0.1.6, the functionality of a couple of the system images were consolidated into a single
rancher/rke-tools image to simplify and speed the deployment process.
You can configure the network plug-ins, ingress controller and dns provider as well as the options for these add-ons separately in the
Below is an example of the list of system images used to deploy Kubernetes through RKE. The default versions of Kubernetes are tied to specific versions of system images.
For RKE v0.2.x and below, the map of versions and the system image versions is located here: https://github.com/rancher/types/blob/release/v2.2/apis/management.cattle.io/v3/k8s_defaults.go
For RKE v0.3.0 and above, the map of versions and the system image versions is located here: https://github.com/rancher/kontainer-driver-metadata/blob/release-v2.7/rke/k8s_rke_system_images.go
As versions of RKE are released, the tags on these images will no longer be up to date. This list is specific for
# kube-dns images
# CoreDNS images
# Flannel images
# Calico images
# Canal images
# Weave images
# Ingress controller images
# Metrics server image
v0.1.6, instead of using the
rancher/rke-tools image, we used the following images:
If you have an air-gapped setup and cannot access
docker.io, you will need to set up your private registry in your cluster configuration file. After you set up private registry, you will need to update these images to pull from your private registry.