Illumina Innovates with Rancher and Kubernetes
Important: RKE add-on install is only supported up to Rancher v2.0.8 Please use the Rancher helm chart to install HA Rancher. For details, see the HA Install - Installation Outline. If you are currently using the RKE add-on install method, see Migrating from an HA RKE Add-on Install for details on how to move to using the helm chart.
Please use the Rancher helm chart to install HA Rancher. For details, see the HA Install - Installation Outline.
If you are currently using the RKE add-on install method, see Migrating from an HA RKE Add-on Install for details on how to move to using the helm chart.
If you operate Rancher behind a proxy and you want to access services through the proxy (such as retrieving catalogs), you must provide Rancher information about your proxy. As Rancher is written in Go, it uses the common proxy environment variables as shown below.
Make sure NO_PROXY contains the network addresses, network address ranges and domains that should be excluded from using the proxy.
NO_PROXY
Note NO_PROXY must be in uppercase to use network range (CIDR) notation.
When using High Availability Installation, the environment variables need to be added to the RKE Config File template.
The environment variables should be defined in the Deployment inside the RKE Config File Template. You only have to add the part starting with env: to (but not including) ports:. Make sure the indentation is identical to the preceding name:. Required values for NO_PROXY are:
Deployment
env:
ports:
name:
localhost
127.0.0.1
0.0.0.0
service_cluster_ip_range
10.43.0.0/16
The example below is based on a proxy server accessible at http://192.168.0.1:3128, and excluding usage of the proxy when accessing network range 192.168.10.0/24, the configured service_cluster_ip_range (10.43.0.0/16) and every hostname under the domain example.com. If you have changed the service_cluster_ip_range, you have to update the value below accordingly.
http://192.168.0.1:3128
192.168.10.0/24
example.com
... --- kind: Deployment apiVersion: extensions/v1beta1 metadata: namespace: cattle-system name: cattle spec: replicas: 1 template: metadata: labels: app: cattle spec: serviceAccountName: cattle-admin containers: - image: rancher/rancher:latest imagePullPolicy: Always name: cattle-server env: - name: HTTP_PROXY value: "http://192.168.10.1:3128" - name: HTTPS_PROXY value: "http://192.168.10.1:3128" - name: NO_PROXY value: "localhost,127.0.0.1,0.0.0.0,10.43.0.0/16,192.168.10.0/24,example.com" ports: ...