Merge pull request #836 from MBishop17/windows-support

Windows support
2026-09-23 19:48:05 +00:00 · 2018-09-28 15:26:43 -07:00
parent 6aa95a2c36 2c7b45b4ef
commit 2612dbee52
14 changed files with 412 additions and 16 deletions
@@ -8,25 +8,25 @@ aliases:

 ## Custom Nodes

-Use Rancher to create a Kubernetes cluster on your on-premise bare metal servers. This option creates a cluster using a combination of <a href='https://docs.docker.com/machine/' target='_blank'>Docker Machine</a> and RKE, which is Rancher's own lightweight Kubernetes installer. In addition to bare metal servers, RKE can also create clusters on _any_ IaaS providers by integrating with node drivers.
+Use Rancher to create a Kubernetes cluster on your on-premise bare metal servers. This option creates a cluster using a combination of [Docker Machine](https://docs.docker.com/machine/) and RKE, which is Rancher's own lightweight Kubernetes installer. In addition to bare metal servers, RKE can also create clusters on _any_ IaaS providers by integrating with node drivers.

 To use this option you'll need access to servers you intend to use as your Kubernetes cluster. Provision each server according to Rancher [requirements](#requirements), which includes some hardware specifications and Docker. After you install Docker on each server, run the command provided in the Rancher UI to turn each server into a Kubernetes node.

 ## Objectives for Creating Cluster with Custom Nodes

-1.	[Provision a Linux Host](#provision-a-linux-host)
+>**Want to use Windows hosts as Kubernetes workers?**
+>
+>See [Configuring Custom Clusters for Windows]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/windows-clusters/) before you start.

-	Begin by provisioning a Linux host.
+<!-- TOC -->

-2. [Create the Cluster](#create-the-custom-cluster)
+- [1. Provision a Linux Host](#1-provision-a-linux-host)
+- [2. Create the Custom Cluster](#2-create-the-custom-cluster)
+- [3. Amazon Only: Tag Resources](#3-amazon-only-tag-resources)

-	Use your new Linux host as a template for your new Kubernetes cluster.
+<!-- /TOC -->

-2. **Amazon Only:** [Tag Resources](#amazon-only-br-tag-resources)
-
-	If you're using Amazon to create your custom cluster, log into AWS and tag your resources with a cluster ID.
-
-## Provision a Linux Host
+## 1. Provision a Linux Host

 Begin creation of a custom cluster by provisioning a Linux host. Your host can be:

@@ -44,7 +44,7 @@ Provision the host according to the requirements below.

 Each node in your cluster must meet our [Requirements]({{< baseurl >}}/rancher/v2.x/en/installation/requirements).

-## Create the Custom Cluster
+## 2. Create the Custom Cluster

 Use {{< product >}} to clone your Linux host and configure them as Kubernetes nodes.

@@ -58,15 +58,20 @@ Use {{< product >}} to clone your Linux host and configure them as Kubernetes no

 5. {{< step_create-cluster_cluster-options >}}

-6.	Click **Next**.
+    >**Using Windows nodes as Kubernetes workers?** 
+    >
+    >- See [Enable the Windows Support Option]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/windows-clusters/#enable-the-windows-support-option).
+    >- The only Network Provider available for clusters with Windows support is Flannel. See [Networking Option]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/windows-clusters/#networking-option).
+6.	<a id="step-6"></a>Click **Next**.

 7.	From **Node Role**, choose the roles that you want filled by a cluster node.

-	>**Bare-Metal Server Reminder:**
+	>**Notes:**
 	>
-	If you plan on dedicating bare-metal servers to each role, you must provision a bare-metal server for each role (i.e. provision multiple bare-metal servers).
+    >- Using Windows nodes as Kubernetes workers? See [Node Configuration]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/windows-clusters/#node-configuration).
+	>- Bare-Metal Server Reminder: If you plan on dedicating bare-metal servers to each role, you must provision a bare-metal server for each role (i.e. provision multiple bare-metal servers).

-8.	**Optional**: Add **Labels** to your cluster nodes to help schedule workloads later.
+8.	<a id="step-8"></a>**Optional**: Add **Labels** to your cluster nodes to help schedule workloads later.

 	[Kubernetes Documentation: Labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/)

@@ -80,7 +85,7 @@ Use {{< product >}} to clone your Linux host and configure them as Kubernetes no

 {{< result_create-cluster >}}

-## Amazon Only:<br/>Tag Resources
+## 3. Amazon Only: Tag Resources

 If you have configured your cluster to use Amazon as **Cloud Provider**, tag your AWS resources with a cluster ID.

@@ -0,0 +1,139 @@
+---
+title: Configuring Custom Clusters for Windows 
+weight: 2600
+---
+When provisioning a [custom cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/custom-clusters/) using Rancher, you have the option of configuring it to support Windows Server hosts as Kubernetes workers. Using this feature, you can provision a custom Kubernetes cluster with a mix of Linux and Windows nodes.
+
+>**Notes:**
+>
+>- Windows nodes are experimental and not yet officially supported in Rancher. Therefore, we do not recommend using Windows nodes in a production environment.
+>- For a summary of Kubernetes features supported in Windows, see [Using Windows Server Containers in Kubernetes](https://kubernetes.io/docs/getting-started-guides/windows/#supported-features).
+
+
+## Objectives for Creating Cluster with Windows Support
+
+When setting up a custom cluster with support for Windows nodes and containers, complete the series of tasks below.
+
+<!-- TOC -->
+
+- [1. Provision Hosts](#1-provision-hosts)
+- [2. Create the Custom Cluster](#2-create-the-custom-cluster)
+- [3. Cloud-host VM Networking Configuration](#3-cloud-host-vm-networking-configuration)
+- [4. Adding Windows Workers](#4-adding-windows-workers)
+- [5. Cloud-host VM Routes Configuration](#5-cloud-host-vm-routes-configuration)
+- [Troubleshooting](#troubleshooting)
+
+<!-- /TOC -->
+
+## 1. Provision Hosts
+
+The first thing you should do when provisioning a custom cluster that includes Windows nodes is to prepare your host servers. Provision three nodes according to our [requirements]({{< baseurl >}}/rancher/v2.x/en/installation/requirements/)—two Linux, one Windows. Your hosts can be:
+
+- A cloud-hosted virtual machine (VM)
+- An on-premise VM
+- A bare-metal server 
+
+The table below lists the [Kubernetes role]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/#kubernetes-cluster-node-components) that each node will fill in your cluster, although you won't enable these roles until further along in the configuration process—we're just informing you of each node's purpose.
+
+Node    | Operating System | Future Cluster Role
+--------|------------------|------
+Node 1  | Linux            | [All]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/#control-plane-nodes)
+Node 2  | Windows          | [Worker]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/#worker-nodes)
+Node 3 (Optional) | Linux  | [Worker]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/#worker-nodes) (This node is used for Ingress support) 
+
+
+>**Bare-Metal Server Note:**
+>
+While creating your cluster, you must assign Kubernetes roles to your cluster nodes. If you plan on dedicating bare-metal servers to each role, you must provision a bare-metal server for each role (i.e. provision multiple bare-metal servers).
+
+## 2. Create the Custom Cluster
+
+To create a custom cluster that supports Windows nodes, follow the instructions in [Creating a Cluster with Custom Nodes]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/#2-create-the-custom-cluster), starting from [2. Create the Custom Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/#2-create-the-custom-cluster). While completing the linked instructions, look for steps that requires special actions for Windows nodes, which are flagged with a note. These notes will link back here, to the special Windows instructions listed in the headings below. 
+
+
+### Enable the Windows Support Option
+
+While choosing **Cluster Options**, set **Windows Support (Experimental)** to **Enabled**.
+
+![Enable Windows Support]({{< baseurl >}}/img/rancher/enable-windows-support.png)
+
+After you select this option, resume [Creating a Cluster with Custom Nodes]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/#create-the-custom-cluster) from [step 6]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/#step-6).
+
+### Networking Option
+
+When choosing a network provider for a cluster that supports Windows, the only option available is Flannel, as [host-gw](https://github.com/coreos/flannel/blob/master/Documentation/backends.md#host-gw) is needed for IP routing.
+
+![Flannel]({{< baseurl >}}/img/rancher/flannel.png)
+
+If your nodes are hosted by a cloud provider and you want automation support such as load balancers or persistent storage devices, see [Selecting Cloud Providers]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/options/cloud-providers) for configuration info.
+
+### Node Configuration
+
+The first node in your cluster should be a Linux host that fills the Control Plane role. At minimum, the node must have this role enabled, but we recommend enabling all three. The following table lists our recommended settings (we'll provide the recommended settings for nodes 2 and 3 later).
+
+Option | Setting
+-------|--------
+Node Operating System | Linux
+Node Roles | etcd <br/> Control Plane <br/> Worker
+
+![Recommended Linux Control Plane Configuration]({{< baseurl >}}/img/rancher/linux-control-plane.png)
+
+When you're done with these configurations, resume [Creating a Cluster with Custom Nodes]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/#create-the-custom-cluster) from [step 8]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/#step-8).
+
+
+## 3. Cloud-host VM Networking Configuration
+
+>**Note:** This step only applies to nodes hosted on cloud-hosted virtual machines. If you're using on-premise virtual machines or baremetal servers, skip ahead to [4. Adding Windows Workers](#4-adding-windows-workers).
+
+If you're hosting your nodes on any of the cloud services listed below, you must disable the private IP address checks for both your Linux or Windows hosts on startup. To disable this check for each node, follow the directions provided by each service below.
+
+Service | Directions to disable private IP address checks
+--------|------------------------------------------------
+Amazon EC2 | [Disabling Source/Destination Checks](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_NAT_Instance.html#EIP_Disable_SrcDestCheck)
+Google GCE | [Enabling IP Forwarding for Instances](https://cloud.google.com/vpc/docs/using-routes#canipforward)
+Azure VM | [Enable or Disable IP Forwarding](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface#enable-or-disable-ip-forwarding)
+
+## 4. Adding Windows Workers
+
+After the initial provisioning of your custom cluster, you cluster only has a single Linux host. You still have to Windows workers to it. Add nodes using the instructions below.
+
+1. From the main menu, select **Nodes**. 
+
+1. Click **Edit Cluster**.
+
+1. Scroll down to **Node Operating System**. Choose **Windows**.
+
+1. Select the **Worker** role.
+
+1. Copy the command displayed on screen to your clipboard.
+
+1. Log in to your Windows host using your preferred tool, such as [Microsoft Remote Desktop](https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-clients). Run the command copied to your clipboard in the **Command Prompt (CMD)**.
+
+1. Repeat these instruction for each Windows host you want to use as a worker node.
+
+**Result:** The worker role is installed on your Windows host, and the node registers with Rancher.
+
+>**Tip:** If you want the cluster that uses Windows workers to include Ingress support, add one more Linux node to the cluster, enabling the worker role on it.
+
+
+## 5. Cloud-host VM Routes Configuration
+
+>**Note:** This step only applies to nodes hosted on cloud-hosted virtual machines. If you're using on-premise virtual machines or baremetal servers, you're done!
+
+If you're hosting your nodes using a service listed in the table below, you must make additional node configurations to account for routing. Follow the vendor instructions provided.
+
+Service | Instructions
+--------|-------------
+Google GCE | For GCE, add a static route for each node: [Adding a Static Route](https://cloud.google.com/vpc/docs/using-routes#addingroute).
+Azure VM | For Azure, create a routing table: [Custom Routes: User-defined](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-udr-overview#user-defined).
+
+To confirm the destination address of each route, you can run this script using [kubectl]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/kubectl): `kubectl get nodes -o custom-columns=nodeName:.metadata.name,nodeIP:status.addresses[0].address,routeDestination:.spec.podCIDR` 
+
+
+### Troubleshooting
+
+If the Windows worker is already starting (i.e., Terminal outputs `Starting plan monitor`), yet it displays a status of `Unavailable` in the Rancher UI, try to restarting the Nginx proxy on the Windows host using the following Docker command:
+
+```
+docker restart nginx-proxy
+```
@@ -13,6 +13,7 @@ Rancher is supported on the following operating systems and their subsequent rel
 *   Ubuntu 16.04 (64-bit)
 *   Red Hat Enterprise Linux 7.5 (64-bit)
 *   RancherOS 1.4 (64-bit)
+*   Windows Server version 1803 (64-bit)

 If you are using RancherOS, make sure you switch the Docker engine to a supported version using:<br>
 `sudo ros engine switch docker-17.03.2-ce`
@@ -61,6 +62,7 @@ Supported Versions:
 *   `1.12.6`
 *   `1.13.1`
 *   `17.03.2`
+*   `17.06` (for Windows)

 If you are using RancherOS, make sure you switch the Docker engine to a supported version using:<br>
 `sudo ros engine switch docker-17.03.2-ce`
@@ -0,0 +1,43 @@
+When setting up an airgap environment, it may be useful to run RKE through a bastion server. This can be helpful if you want to keep your RKE config or SSH keys on your local machine. This requires that the bastion server is accessible from the outside world, and has access to port 22 (SSH) on your airgapped nodes. 
+
+local RKE (via port 22 over internet) -> bastion
+bastion (via port 22 over internal network) -> airgap_node_1, airgap_node_2, airgap_node3 
+
+To enable running RKE through a bastion server, add the following to your RKE yaml config:
+
+```
+bastion_host:
+    address: 18.224.54.35 # public IP of the bastion server
+    user: ubuntu
+    port: 22
+    ssh_key_path: /path/to/ssh/key
+```
+
+Full ex: 
+```
+bastion_host:
+    address: 18.224.54.35 # public IP of the bastion server
+    user: ubuntu
+    port: 22
+    ssh_key_path: /path/to/ssh/key
+nodes:
+ - address: 172.31.6.15 # private IP of airgapped node
+   user: ubuntu
+   role: [ "controlplane", "etcd", "worker" ]
+   ssh_key_path: /path/to/ssh/key
+ - address: 172.31.12.84 # private IP of airgapped node
+   user: ubuntu
+   role: [ "controlplane", "etcd", "worker" ]
+   ssh_key_path: /path/to/ssh/key
+ - address: 172.31.15.78 # private IP of airgapped node
+   user: ubuntu
+   role: [ "controlplane", "etcd", "worker" ]
+   ssh_key_path: /path/to/ssh/key
+private_registries:
+ - url: <registry url>
+   user: <username>
+   password: <password>
+   is_default: true
+ ```
+
+  Running `rke up` will provision the k8s cluster through the bastion server, and provide the resulting kube_config. However, it's important to note that as your nodes are not accessible via a public IP, the machine you run `kubectl` from in later steps must be able to reach your airgapped nodes through the addresses provided. This may require moving the resulting kube_config after it is created.
@@ -0,0 +1,30 @@
+#!/bin/bash
+set -e
+    
+# Collect images for Air Gap/Private Registry install
+# Requires:
+#   rke - https://rancher.com/docs/rke/v0.1.x/en/installation/
+#   helm - https://docs.helm.sh/using_helm/#installing-helm
+#   curl
+#   jq
+    
+echo "RKE Images"
+rke config --system-images 2>/dev/null > tmp-images.txt
+    
+echo "Helm Tiller Image"
+helm init --dry-run --debug | grep image: | awk '{print $2}' >> tmp-images.txt
+    
+echo "Rancher Images"
+latest_url=$(curl -sS "https://api.github.com/repos/rancher/rancher/releases/latest" | jq -r '.assets[]|select(.name=="rancher-images.txt")|.browser_download_url')
+curl -sSL ${latest_url} >> tmp-images.txt
+    
+echo "Cert-Manager Image"
+cm_repo=$(helm inspect values stable/cert-manager | grep repository: | awk '{print $2}')
+cm_tag=$(helm inspect values stable/cert-manager | grep tag: | awk '{print $2}')
+echo "${cm_repo}:${cm_tag}" >> tmp-images.txt
+    
+echo "Sort and uniq the images list"
+cat tmp-images.txt | sort -u | uniq > images.txt
+    
+# cleanup tmp file
+rm tmp-images.txt
@@ -0,0 +1,40 @@
+busybox
+rancher/alertmanager-helper:v0.0.2
+rancher/alpine-git:1.0.4
+rancher/calico-cni:v3.1.1
+rancher/calico-ctl:v2.0.0
+rancher/calico-node:v3.1.1
+rancher/cluster-proportional-autoscaler-amd64:1.0.0
+rancher/coreos-etcd:v3.1.12
+rancher/coreos-etcd:v3.2.18
+rancher/coreos-flannel-cni:v0.2.0
+rancher/coreos-flannel:v0.9.1
+rancher/docker-elasticsearch-kubernetes:5.6.2
+rancher/fluentd-helper:v0.1.2
+rancher/fluentd:v0.1.10
+rancher/hyperkube:v1.10.5-rancher1
+rancher/hyperkube:v1.11.2-rancher1
+rancher/hyperkube:v1.9.7-rancher2
+rancher/jenkins-jenkins:2.107-slim
+rancher/jenkins-jnlp-slave:3.10-1-alpine
+rancher/jenkins-plugins-docker:17.12
+rancher/k8s-dns-dnsmasq-nanny-amd64:1.14.10
+rancher/k8s-dns-dnsmasq-nanny-amd64:1.14.7
+rancher/k8s-dns-dnsmasq-nanny-amd64:1.14.8
+rancher/k8s-dns-kube-dns-amd64:1.14.10
+rancher/k8s-dns-kube-dns-amd64:1.14.7
+rancher/k8s-dns-kube-dns-amd64:1.14.8
+rancher/k8s-dns-sidecar-amd64:1.14.10
+rancher/k8s-dns-sidecar-amd64:1.14.7
+rancher/k8s-dns-sidecar-amd64:1.14.8
+rancher/kibana:5.6.4
+rancher/log-aggregator:v0.1.3
+rancher/metrics-server-amd64:v0.2.1
+rancher/nginx-ingress-controller-defaultbackend:1.4
+rancher/nginx-ingress-controller:0.16.2-rancher1
+rancher/pause-amd64:3.0
+rancher/pause-amd64:3.1
+rancher/prom-alertmanager:v0.11.0
+rancher/rke-tools:v0.1.13
+rancher/rancher:v2.0.8
+rancher/rancher-agent:v2.0.8
@@ -0,0 +1,93 @@
+#!/bin/sh
+
+if [ -z "$1" ]; then
+  echo Usage: $0 [REGISTRY]
+  exit 1
+fi
+
+set -e -x
+REGISTRY=$1
+
+docker load --input rancher-images.tar.gz
+
+
+docker tag busybox ${REGISTRY}/busybox
+docker push ${REGISTRY}/busybox
+docker tag rancher/alertmanager-helper:v0.0.2 ${REGISTRY}/rancher/alertmanager-helper:v0.0.2
+docker push ${REGISTRY}/rancher/alertmanager-helper:v0.0.2
+docker tag rancher/alpine-git:1.0.4 ${REGISTRY}/rancher/alpine-git:1.0.4
+docker push ${REGISTRY}/rancher/alpine-git:1.0.4
+docker tag rancher/calico-cni:v3.1.1 ${REGISTRY}/rancher/calico-cni:v3.1.1
+docker push ${REGISTRY}/rancher/calico-cni:v3.1.1
+docker tag rancher/calico-ctl:v2.0.0 ${REGISTRY}/rancher/calico-ctl:v2.0.0
+docker push ${REGISTRY}/rancher/calico-ctl:v2.0.0
+docker tag rancher/calico-node:v3.1.1 ${REGISTRY}/rancher/calico-node:v3.1.1
+docker push ${REGISTRY}/rancher/calico-node:v3.1.1
+docker tag rancher/cluster-proportional-autoscaler-amd64:1.0.0 ${REGISTRY}/rancher/cluster-proportional-autoscaler-amd64:1.0.0
+docker push ${REGISTRY}/rancher/cluster-proportional-autoscaler-amd64:1.0.0
+docker tag rancher/coreos-etcd:v3.1.12 ${REGISTRY}/rancher/coreos-etcd:v3.1.12
+docker push ${REGISTRY}/rancher/coreos-etcd:v3.1.12
+docker tag rancher/coreos-etcd:v3.2.18 ${REGISTRY}/rancher/coreos-etcd:v3.2.18
+docker push ${REGISTRY}/rancher/coreos-etcd:v3.2.18
+docker tag rancher/coreos-flannel-cni:v0.2.0 ${REGISTRY}/rancher/coreos-flannel-cni:v0.2.0
+docker push ${REGISTRY}/rancher/coreos-flannel-cni:v0.2.0
+docker tag rancher/coreos-flannel:v0.9.1 ${REGISTRY}/rancher/coreos-flannel:v0.9.1
+docker push ${REGISTRY}/rancher/coreos-flannel:v0.9.1
+docker tag rancher/docker-elasticsearch-kubernetes:5.6.2 ${REGISTRY}/rancher/docker-elasticsearch-kubernetes:5.6.2
+docker push ${REGISTRY}/rancher/docker-elasticsearch-kubernetes:5.6.2
+docker tag rancher/fluentd-helper:v0.1.2 ${REGISTRY}/rancher/fluentd-helper:v0.1.2
+docker push ${REGISTRY}/rancher/fluentd-helper:v0.1.2
+docker tag rancher/fluentd:v0.1.10 ${REGISTRY}/rancher/fluentd:v0.1.10
+docker push ${REGISTRY}/rancher/fluentd:v0.1.10
+docker tag rancher/hyperkube:v1.10.5-rancher1 ${REGISTRY}/rancher/hyperkube:v1.10.5-rancher1
+docker push ${REGISTRY}/rancher/hyperkube:v1.10.5-rancher1
+docker tag rancher/hyperkube:v1.11.2-rancher1 ${REGISTRY}/rancher/hyperkube:v1.11.2-rancher1
+docker push ${REGISTRY}/rancher/hyperkube:v1.11.2-rancher1
+docker tag rancher/hyperkube:v1.9.7-rancher2 ${REGISTRY}/rancher/hyperkube:v1.9.7-rancher2
+docker push ${REGISTRY}/rancher/hyperkube:v1.9.7-rancher2
+docker tag rancher/jenkins-jenkins:2.107-slim ${REGISTRY}/rancher/jenkins-jenkins:2.107-slim
+docker push ${REGISTRY}/rancher/jenkins-jenkins:2.107-slim
+docker tag rancher/jenkins-jnlp-slave:3.10-1-alpine ${REGISTRY}/rancher/jenkins-jnlp-slave:3.10-1-alpine
+docker push ${REGISTRY}/rancher/jenkins-jnlp-slave:3.10-1-alpine
+docker tag rancher/jenkins-plugins-docker:17.12 ${REGISTRY}/rancher/jenkins-plugins-docker:17.12
+docker push ${REGISTRY}/rancher/jenkins-plugins-docker:17.12
+docker tag rancher/k8s-dns-dnsmasq-nanny-amd64:1.14.10 ${REGISTRY}/rancher/k8s-dns-dnsmasq-nanny-amd64:1.14.10
+docker push ${REGISTRY}/rancher/k8s-dns-dnsmasq-nanny-amd64:1.14.10
+docker tag rancher/k8s-dns-dnsmasq-nanny-amd64:1.14.7 ${REGISTRY}/rancher/k8s-dns-dnsmasq-nanny-amd64:1.14.7
+docker push ${REGISTRY}/rancher/k8s-dns-dnsmasq-nanny-amd64:1.14.7
+docker tag rancher/k8s-dns-dnsmasq-nanny-amd64:1.14.8 ${REGISTRY}/rancher/k8s-dns-dnsmasq-nanny-amd64:1.14.8
+docker push ${REGISTRY}/rancher/k8s-dns-dnsmasq-nanny-amd64:1.14.8
+docker tag rancher/k8s-dns-kube-dns-amd64:1.14.10 ${REGISTRY}/rancher/k8s-dns-kube-dns-amd64:1.14.10
+docker push ${REGISTRY}/rancher/k8s-dns-kube-dns-amd64:1.14.10
+docker tag rancher/k8s-dns-kube-dns-amd64:1.14.7 ${REGISTRY}/rancher/k8s-dns-kube-dns-amd64:1.14.7
+docker push ${REGISTRY}/rancher/k8s-dns-kube-dns-amd64:1.14.7
+docker tag rancher/k8s-dns-kube-dns-amd64:1.14.8 ${REGISTRY}/rancher/k8s-dns-kube-dns-amd64:1.14.8
+docker push ${REGISTRY}/rancher/k8s-dns-kube-dns-amd64:1.14.8
+docker tag rancher/k8s-dns-sidecar-amd64:1.14.10 ${REGISTRY}/rancher/k8s-dns-sidecar-amd64:1.14.10
+docker push ${REGISTRY}/rancher/k8s-dns-sidecar-amd64:1.14.10
+docker tag rancher/k8s-dns-sidecar-amd64:1.14.7 ${REGISTRY}/rancher/k8s-dns-sidecar-amd64:1.14.7
+docker push ${REGISTRY}/rancher/k8s-dns-sidecar-amd64:1.14.7
+docker tag rancher/k8s-dns-sidecar-amd64:1.14.8 ${REGISTRY}/rancher/k8s-dns-sidecar-amd64:1.14.8
+docker push ${REGISTRY}/rancher/k8s-dns-sidecar-amd64:1.14.8
+docker tag rancher/kibana:5.6.4 ${REGISTRY}/rancher/kibana:5.6.4
+docker push ${REGISTRY}/rancher/kibana:5.6.4
+docker tag rancher/log-aggregator:v0.1.3 ${REGISTRY}/rancher/log-aggregator:v0.1.3
+docker push ${REGISTRY}/rancher/log-aggregator:v0.1.3
+docker tag rancher/metrics-server-amd64:v0.2.1 ${REGISTRY}/rancher/metrics-server-amd64:v0.2.1
+docker push ${REGISTRY}/rancher/metrics-server-amd64:v0.2.1
+docker tag rancher/nginx-ingress-controller-defaultbackend:1.4 ${REGISTRY}/rancher/nginx-ingress-controller-defaultbackend:1.4
+docker push ${REGISTRY}/rancher/nginx-ingress-controller-defaultbackend:1.4
+docker tag rancher/nginx-ingress-controller:0.16.2-rancher1 ${REGISTRY}/rancher/nginx-ingress-controller:0.16.2-rancher1
+docker push ${REGISTRY}/rancher/nginx-ingress-controller:0.16.2-rancher1
+docker tag rancher/pause-amd64:3.0 ${REGISTRY}/rancher/pause-amd64:3.0
+docker push ${REGISTRY}/rancher/pause-amd64:3.0
+docker tag rancher/pause-amd64:3.1 ${REGISTRY}/rancher/pause-amd64:3.1
+docker push ${REGISTRY}/rancher/pause-amd64:3.1
+docker tag rancher/prom-alertmanager:v0.11.0 ${REGISTRY}/rancher/prom-alertmanager:v0.11.0
+docker push ${REGISTRY}/rancher/prom-alertmanager:v0.11.0
+docker tag rancher/rke-tools:v0.1.13 ${REGISTRY}/rancher/rke-tools:v0.1.13
+docker push ${REGISTRY}/rancher/rke-tools:v0.1.13
+docker tag rancher/rancher:v2.0.8 ${REGISTRY}/rancher/rancher:v2.0.8
+docker push ${REGISTRY}/rancher/rancher:v2.0.8
+docker tag rancher/rancher-agent:v2.0.8 ${REGISTRY}/rancher/rancher-agent:v2.0.8
+docker push ${REGISTRY}/rancher/rancher-agent:v2.0.8
@@ -0,0 +1,44 @@
+#!/bin/sh
+set -e -x
+
+docker pull busybox
+docker pull rancher/alertmanager-helper:v0.0.2
+docker pull rancher/alpine-git:1.0.4
+docker pull rancher/calico-cni:v3.1.1
+docker pull rancher/calico-ctl:v2.0.0
+docker pull rancher/calico-node:v3.1.1
+docker pull rancher/cluster-proportional-autoscaler-amd64:1.0.0
+docker pull rancher/coreos-etcd:v3.1.12
+docker pull rancher/coreos-etcd:v3.2.18
+docker pull rancher/coreos-flannel-cni:v0.2.0
+docker pull rancher/coreos-flannel:v0.9.1
+docker pull rancher/docker-elasticsearch-kubernetes:5.6.2
+docker pull rancher/fluentd-helper:v0.1.2
+docker pull rancher/fluentd:v0.1.10
+docker pull rancher/hyperkube:v1.10.5-rancher1
+docker pull rancher/hyperkube:v1.11.2-rancher1
+docker pull rancher/hyperkube:v1.9.7-rancher2
+docker pull rancher/jenkins-jenkins:2.107-slim
+docker pull rancher/jenkins-jnlp-slave:3.10-1-alpine
+docker pull rancher/jenkins-plugins-docker:17.12
+docker pull rancher/k8s-dns-dnsmasq-nanny-amd64:1.14.10
+docker pull rancher/k8s-dns-dnsmasq-nanny-amd64:1.14.7
+docker pull rancher/k8s-dns-dnsmasq-nanny-amd64:1.14.8
+docker pull rancher/k8s-dns-kube-dns-amd64:1.14.10
+docker pull rancher/k8s-dns-kube-dns-amd64:1.14.7
+docker pull rancher/k8s-dns-kube-dns-amd64:1.14.8
+docker pull rancher/k8s-dns-sidecar-amd64:1.14.10
+docker pull rancher/k8s-dns-sidecar-amd64:1.14.7
+docker pull rancher/k8s-dns-sidecar-amd64:1.14.8
+docker pull rancher/kibana:5.6.4
+docker pull rancher/log-aggregator:v0.1.3
+docker pull rancher/metrics-server-amd64:v0.2.1
+docker pull rancher/nginx-ingress-controller-defaultbackend:1.4
+docker pull rancher/nginx-ingress-controller:0.16.2-rancher1
+docker pull rancher/pause-amd64:3.0
+docker pull rancher/pause-amd64:3.1
+docker pull rancher/prom-alertmanager:v0.11.0
+docker pull rancher/rke-tools:v0.1.13
+docker pull rancher/rancher:v2.0.8
+docker pull rancher/rancher-agent:v2.0.8
+docker save busybox rancher/alertmanager-helper:v0.0.2 rancher/alpine-git:1.0.4 rancher/calico-cni:v3.1.1 rancher/calico-ctl:v2.0.0 rancher/calico-node:v3.1.1 rancher/cluster-proportional-autoscaler-amd64:1.0.0 rancher/coreos-etcd:v3.1.12 rancher/coreos-etcd:v3.2.18 rancher/coreos-flannel-cni:v0.2.0 rancher/coreos-flannel:v0.9.1 rancher/docker-elasticsearch-kubernetes:5.6.2 rancher/fluentd-helper:v0.1.2 rancher/fluentd:v0.1.10 rancher/hyperkube:v1.10.5-rancher1 rancher/hyperkube:v1.11.2-rancher1 rancher/hyperkube:v1.9.7-rancher2 rancher/jenkins-jenkins:2.107-slim rancher/jenkins-jnlp-slave:3.10-1-alpine rancher/jenkins-plugins-docker:17.12 rancher/k8s-dns-dnsmasq-nanny-amd64:1.14.10 rancher/k8s-dns-dnsmasq-nanny-amd64:1.14.7 rancher/k8s-dns-dnsmasq-nanny-amd64:1.14.8 rancher/k8s-dns-kube-dns-amd64:1.14.10 rancher/k8s-dns-kube-dns-amd64:1.14.7 rancher/k8s-dns-kube-dns-amd64:1.14.8 rancher/k8s-dns-sidecar-amd64:1.14.10 rancher/k8s-dns-sidecar-amd64:1.14.7 rancher/k8s-dns-sidecar-amd64:1.14.8 rancher/kibana:5.6.4 rancher/log-aggregator:v0.1.3 rancher/metrics-server-amd64:v0.2.1 rancher/nginx-ingress-controller-defaultbackend:1.4 rancher/nginx-ingress-controller:0.16.2-rancher1 rancher/pause-amd64:3.0 rancher/pause-amd64:3.1 rancher/prom-alertmanager:v0.11.0 rancher/rke-tools:v0.1.13 rancher/rancher:v2.0.8 rancher/rancher-agent:v2.0.8 | gzip -c > rancher-images.tar.gz