diff --git a/content/rke/v0.1.x/en/config-options/private-registries/_index.md b/content/rke/v0.1.x/en/config-options/private-registries/_index.md index 4ac21ed02f7..05d339692c5 100644 --- a/content/rke/v0.1.x/en/config-options/private-registries/_index.md +++ b/content/rke/v0.1.x/en/config-options/private-registries/_index.md @@ -1,9 +1,11 @@ --- title: Private Registries -weight: 3000 +weight: 3010 draft: true --- -RKE supports configuring multiple private/authenticated Docker registries. This is useful if you have private images to use or are deploying your cluster in an air-gapped environment. + +RKE supports the ability to configure multiple private Docker registries. By passing in your registry and credentials, it allows the nodes to pull images from these private registries. + ```yaml private_registries: - url: registry.com @@ -13,3 +15,7 @@ private_registries: user: myuser password: mypassword ``` + +### Air-gapped Setups + +If you are in an air-gapped setup, you will need to not only configure your private registry credentials, but you will need to also update all your [system images]({{< baseurl >}}/rke/v0.1.x/en/config-options/system-images/) so they are going to pull from the private registry. By default, these system images are pulling from `docker.io`. diff --git a/content/rke/v0.1.x/en/config-options/system-images/_index.md b/content/rke/v0.1.x/en/config-options/system-images/_index.md index a6b3a0ff0a7..7c5175eb001 100644 --- a/content/rke/v0.1.x/en/config-options/system-images/_index.md +++ b/content/rke/v0.1.x/en/config-options/system-images/_index.md @@ -1,59 +1,57 @@ --- title: System Images -weight: 3000 +weight: 3020 draft: true --- -RKE pulls several images during it's operation. Both for actual system components and to perform deployment actions. +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. + +As of `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. + +This is the example of the full list of system images used to deploy Kubernetes through RKE. The image tags are dependent on the [Kubernetes image/version used](https://github.com/rancher/types/blob/master/apis/management.cattle.io/v3/k8s_defaults.go). + +> **Note:** As versions of RKE are released, the tags on these images will no longer be up to date. This list is specific for `v1.10.3-rancher2`. + +```yaml +system_images: + kubernetes: rancher/hyperkube:v1.10.3-rancher2 + etcd: rancher/coreos-etcd:v3.1.12 + alpine: rancher/rke-tools:v0.1.9 + nginx_proxy: rancher/rke-tools:v0.1.9 + cert_downloader: rancher/rke-tools:v0.1.9 + kubernetes_services_sidecar: rancher/rke-tools:v0.1.9 + kubedns: rancher/k8s-dns-kube-dns-amd64:1.14.8 + dnsmasq: rancher/k8s-dns-dnsmasq-nanny-amd64:1.14.8 + kubedns_sidecar: rancher/k8s-dns-sidecar-amd64:1.14.8 + kubedns_autoscaler: rancher/cluster-proportional-autoscaler-amd64:1.0.0 + pod_infra_container: rancher/pause-amd64:3.1 + + # Networking Options + flannel: rancher/coreos-flannel:v0.9.1 + flannel_cni: rancher/coreos-flannel-cni:v0.2.0 + calico_node: rancher/calico-node:v3.1.1 + calico_cni: rancher/calico-cni:v3.1.1 + calico_ctl: rancher/calico-ctl:v2.0.0 + canal_node: rancher/calico-node:v3.1.1 + canal_cni: rancher/calico-cni:v3.1.1 + canal_flannel: rancher/coreos-flannel:v0.9.1 + weave_node: weaveworks/weave-kube:2.1.2 + weave_cni: weaveworks/weave-npc:2.1.2 + + # Ingress OPTIONS + ingress: rancher/nginx-ingress-controller:0.10.2-rancher3 + ingressBackend: rancher/nginx-ingress-controller-defaultbackend:1.4 +``` + +Prior to `v0.1.6`, instead of using the `rancher/rke-tools` image, we used the following images: -Prior to version `0.1.6`, RKE used the following list of images for deployment and cluster configuration: ```yaml system_images: - etcd: rancher/etcd:v3.0.17 - kubernetes: rancher/k8s:v1.8.9-rancher1-1 alpine: alpine:latest nginx_proxy: rancher/rke-nginx-proxy:v0.1.1 cert_downloader: rancher/rke-cert-deployer:v0.1.1 kubernetes_services_sidecar: rancher/rke-service-sidekick:v0.1.0 - kubedns: rancher/k8s-dns-kube-dns-amd64:1.14.5 - dnsmasq: rancher/k8s-dns-dnsmasq-nanny-amd64:1.14.5 - kubedns_sidecar: rancher/k8s-dns-sidecar-amd64:1.14.5 - kubedns_autoscaler: rancher/cluster-proportional-autoscaler-amd64:1.0.0 ``` -In addintion to the above list, images for the network plugin were also pulled. The exact network plugin images depend on the configured plugin and it's version. +### Air-gapped Setups - -As of version `0.1.6`, the functionality of several system images were consolidated into a single `rke-tools` image to simplify and speed the deployment process. - -The following images are no longer used. They are replaced by `rancher/rke-tools`: -- alpine:latest -- rancher/rke-nginx-proxy:v0.1.1 -- rancher/rke-cert-deployer:v0.1.1 -- rancher/rke-service-sidekick:v0.1.0 - -This as of version `v0.1.8`, this is a full list of images and values: -```yaml -etcd: rancher/coreos-etcd:v3.1.12 -alpine: rancher/rke-tools:v0.1.9 -nginx_proxy: rancher/rke-tools:v0.1.9 -cert_downloader: rancher/rke-tools:v0.1.9 -kubernetes_services_sidecar: rancher/rke-tools:v0.1.9 -kubedns: rancher/k8s-dns-kube-dns-amd64:1.14.8 -dnsmasq: rancher/k8s-dns-dnsmasq-nanny-amd64:1.14.8 -kubednsSidecar: rancher/k8s-dns-sidecar-amd64:1.14.8 -kubednsAutoscaler: rancher/cluster-proportional-autoscaler-amd64:1.0.0 -kubernetes: rancher/hyperkube:v1.10.3-rancher2 -flannel: rancher/coreos-flannel:v0.9.1 -flannelCNI: rancher/coreos-flannel-cni:v0.2.0 -calico_node: rancher/calico-node:v3.1.1 -calico_cni: rancher/calico-cni:v3.1.1 -calico_ctl: rancher/calico-ctl:v2.0.0 -canal_node: rancher/calico-node:v3.1.1 -canal_cni: rancher/calico-cni:v3.1.1 -Canalflannel: rancher/coreos-flannel:v0.9.1 -wave_node: weaveworks/weave-kube:2.1.2 -weave_cni: weaveworks/weave-npc:2.1.2 -pod_infra_container: rancher/pause-amd64:3.1 -ingress: rancher/nginx-ingress-controller:0.10.2-rancher3 -ingressBackend: rancher/nginx-ingress-controller-defaultbackend:1.4 -``` +If you have an air-gapped setup and cannot access `docker.io`, you will need to set up your [private registry]({{< baseurl >}}/rke/v0.1.x/en/config-options/private-registries/) in your cluster configuration file. After you set up private registry, you will need to update these images to pull from your private registry.