mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-25 12:38:05 +00:00
add air gap/private regsitry instructions
This commit is contained in:
@@ -24,7 +24,7 @@ This procedure walks you through setting up a 3-node cluster with RKE and instal
|
||||
The following CLI tools are required for this install. Please make sure these tools installed and available in your `$PATH`
|
||||
|
||||
* [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-kubectl) - Kubernetes command-line tool.
|
||||
* [rke]({{< baseurl >}}docs/rke/v0.1.x/en/installation/) - Rancher Kubernetes Engine, cli for building Kubernetes clusters.
|
||||
* [rke]({{< baseurl >}}/rke/v0.1.x/en/installation/) - Rancher Kubernetes Engine, cli for building Kubernetes clusters.
|
||||
* [helm](https://docs.helm.sh/using_helm/#installing-helm) - Package management for Kubernetes.
|
||||
|
||||
## Installation Outline
|
||||
|
||||
@@ -16,7 +16,47 @@ weight: 276
|
||||
```
|
||||
kubectl -n kube-system create serviceaccount tiller
|
||||
kubectl create clusterrolebinding tiller --clusterrole cluster-admin --serviceaccount=kube-system:tiller
|
||||
```
|
||||
|
||||
<details><summary>Additional steps for Air Gap/Private Registry</summary>
|
||||
<p>
|
||||
|
||||
If you have an Air Gapped network extra configuration will be required.
|
||||
|
||||
##### Create registry secret
|
||||
|
||||
Create a registry secret in the `kube-system` namespace for the `tiller` ServiceAccount to use.
|
||||
|
||||
```
|
||||
kubectl -n kube-system create secret docker-registry regcred \
|
||||
--docker-server="reg.example.com" \
|
||||
--docker-username=<user> \
|
||||
--docker-password=<password> \
|
||||
--docker-email=<email>
|
||||
```
|
||||
|
||||
##### Patch the ServiceAccount
|
||||
|
||||
Update the ServiceAccount to include the imagePullSecret. Pods created with this ServiceAccount will automatically have the imagePullSecret added to their manifest.
|
||||
|
||||
```
|
||||
kubectl -n kube-system patch serviceaccount default -p '{\"imagePullSecrets\": [{\"name\": \"regcred\"}]}'
|
||||
```
|
||||
|
||||
##### Helm Init with `--tiller-image` option
|
||||
|
||||
```
|
||||
helm init --service-account tiller --tiller-image registry.example.com/kubernetes-helm/tiller:v2.9.1
|
||||
```
|
||||
|
||||
</p>
|
||||
</details>
|
||||
|
||||
```
|
||||
helm init --service-account tiller
|
||||
```
|
||||
|
||||
> NOTE: This `tiller` install has full cluster access, which should be acceptable if the cluster is dedicated to Rancher server. Check out the [helm docs](https://docs.helm.sh/using_helm/#role-based-access-control) for restricting `tiller` access to suit your security requirements.
|
||||
> NOTE: This `tiller` install has full cluster access, which should be acceptable if the cluster is dedicated to Rancher server. Check out the [helm docs](https://docs.helm.sh/using_helm/#role-based-access-control) for restricting `tiller` access to suit your security requirements.
|
||||
|
||||
|
||||
[Next: Install Rancher]({{< baseurl >}}/rancher/v2.x/en/installation/ha-server-install2/rancher/)
|
||||
@@ -3,7 +3,7 @@ title: 2 - Configure Load Balancer
|
||||
weight: 276
|
||||
---
|
||||
|
||||
Choose a hostname that you will use to access Rancher and
|
||||
Choose a hostname that you will use to access Rancher and Create a DNS record to point at your load balancer endpoint.
|
||||
|
||||
### Load Balancer
|
||||
|
||||
|
||||
@@ -28,11 +28,11 @@ nodes:
|
||||
|
||||
| Option | Description |
|
||||
| --- | --- |
|
||||
| `address` | The public DNS or IP address |
|
||||
| `internal_address` | The private DNS or IP address for inter-cluster traffic |
|
||||
| `role` | List of Kubernetes roles assigned to the node |
|
||||
| `ssh_key_path` | Path to SSH private key used to authenticate to the node |
|
||||
| `user` | A user that can run docker commands |
|
||||
| `address` | (required) The public DNS or IP address |
|
||||
| `internal_address` | (optional) The private DNS or IP address for internal cluster traffic |
|
||||
| `role` | (required) List of Kubernetes roles assigned to the node |
|
||||
| `ssh_key_path` | (optional) Path to SSH private key used to authenticate to the node |
|
||||
| `user` | (required) A user that can run docker commands |
|
||||
|
||||
<br/>
|
||||
|
||||
@@ -40,10 +40,11 @@ nodes:
|
||||
|
||||
RKE has many configuration options for customizing the install to suit your specific environment. Here are some common advanced scenarios.
|
||||
|
||||
* Air Gap Network
|
||||
* Private Docker Registry
|
||||
* [SSH Bastion/Jump Server]({{< baseurl >}}/rke/v0.1.x/en/config-options/bastion-host/)
|
||||
* [System Images for Air Gap Network]({{< baseurl >}}/rke/v0.1.x/en/config-options/system-images/)
|
||||
* [Private Docker Image Registry]({{< baseurl >}}/rke/v0.1.x/en/config-options/private-registries/)
|
||||
|
||||
Please see the [RKE Documentation]({{< baseurl >}}docs/rke/v0.1.x/en/) for the full list of options and capabilities.
|
||||
Please see the [RKE Documentation]({{< baseurl >}}/rke/v0.1.x/en/) for the full list of options and capabilities.
|
||||
|
||||
### Run RKE
|
||||
|
||||
|
||||
Reference in New Issue
Block a user