Continental Innovates with Rancher and Kubernetes
This section is about how to prepare to launch a Kubernetes cluster which is used to deploy Rancher server for your air gapped environment.
Since a Kubernetes Installation requires a Kubernetes cluster, we will create a Kubernetes cluster using Rancher Kubernetes Engine (RKE). Before being able to start your Kubernetes cluster, you’ll need to install RKE and create a RKE config file.
From a system that can access ports 22/tcp and 6443/tcp on your host nodes, use the sample below to create a new file named rancher-cluster.yml. This file is a Rancher Kubernetes Engine configuration file (RKE config file), which is a configuration for the cluster you’re deploying Rancher to.
rancher-cluster.yml
Replace values in the code sample below with help of the RKE Options table. Use the IP address or DNS names of the 3 nodes you created.
Tip: For more details on the options available, see the RKE Config Options.
address
user
role
internal_address
ssh_key_path
~/.ssh/id_rsa
1 Some services like AWS EC2 require setting the internal_address if you want to use self-referencing security groups or firewalls.
nodes: - address: 10.10.3.187 # node air gap network IP internal_address: 172.31.7.22 # node intra-cluster IP user: rancher role: ['controlplane', 'etcd', 'worker'] ssh_key_path: /home/user/.ssh/id_rsa - address: 10.10.3.254 # node air gap network IP internal_address: 172.31.13.132 # node intra-cluster IP user: rancher role: ['controlplane', 'etcd', 'worker'] ssh_key_path: /home/user/.ssh/id_rsa - address: 10.10.3.89 # node air gap network IP internal_address: 172.31.3.216 # node intra-cluster IP user: rancher role: ['controlplane', 'etcd', 'worker'] ssh_key_path: /home/user/.ssh/id_rsa private_registries: - url: <REGISTRY.YOURDOMAIN.COM:PORT> # private registry url user: rancher password: '*********' is_default: true
After configuring rancher-cluster.yml, bring up your Kubernetes cluster:
rke up --config ./rancher-cluster.yml
Important The files mentioned below are needed to maintain, troubleshoot and upgrade your cluster.
Save a copy of the following files in a secure location:
kube_config_rancher-cluster.yml
rancher-cluster.rkestate
Note: The “rancher-cluster” parts of the two latter file names are dependent on how you name the RKE cluster configuration file.