Skip to content

Commit d2ac60a

Browse files
btatbtat
authored
Merge pull request #4071 from brandond/fix-rke2-tutorial
Fix rke2 tutorial
2 parents 892f780 + 5a00fe3 commit d2ac60a

File tree

1 file changed

+35
-50
lines changed
  • content/rancher/v2.6/en/installation/resources/k8s-tutorials/ha-rke2

1 file changed

+35
-50
lines changed

‎content/rancher/v2.6/en/installation/resources/k8s-tutorials/ha-rke2/_index.md‎

Lines changed: 35 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ To use this `kubeconfig` file,
8989

9090
1. Install [kubectl,](https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-kubectl) a Kubernetes command-line tool.
9191
2. Copy the file at `/etc/rancher/rke2/rke2.yaml` and save it to the directory `~/.kube/config` on your local machine.
92-
3. In the kubeconfig file, the `server` directive is defined as localhost. Configure the server as the DNS of your load balancer, referring to port 6443. (The Kubernetes API server will be reached at port 6443, while the Rancher server will be reached at ports 80 and 443.) Here is an example `rke2.yaml`:
92+
3. In the kubeconfig file, the `server` directive is defined as localhost. Configure the server as the DNS of your control-plane load balancer, on port 6443. (The RKE2 Kubernetes API Server uses port 6443, while the Rancher server will be served via the NGINX Ingress on ports 80 and 443.) Here is an example `rke2.yaml`:
9393

9494
```yml
9595
apiVersion: v1
@@ -128,55 +128,40 @@ Now that you have set up the `kubeconfig` file, you can use `kubectl` to access
128128
Check that all the required pods and containers are healthy are ready to continue:
129129
130130
```
131-
/var/lib/rancher/rke2/bin/kubectl --kubeconfig /etc/rancher/rke2/rke2.yaml get pods -A
132-
NAMESPACE NAME READY STATUS RESTARTS AGE
133-
kube-system etcd-ip-172-31-18-145 1/1 Running 0 4m37s
134-
kube-system etcd-ip-172-31-25-73 1/1 Running 0 20m
135-
kube-system etcd-ip-172-31-31-210 1/1 Running 0 9m12s
136-
kube-system helm-install-rke2-canal-th9k9 0/1 Completed 0 21m
137-
kube-system helm-install-rke2-coredns-6njr6 0/1 Completed 0 21m
138-
kube-system helm-install-rke2-ingress-nginx-vztsd 0/1 Completed 0 21m
139-
kube-system helm-install-rke2-kube-proxy-6std5 0/1 Completed 0 21m
140-
kube-system helm-install-rke2-metrics-server-9sl7m 0/1 Completed 0 21m
141-
kube-system kube-apiserver-ip-172-31-18-145 1/1 Running 0 4m22s
142-
kube-system kube-apiserver-ip-172-31-25-73 1/1 Running 0 20m
143-
kube-system kube-apiserver-ip-172-31-31-210 1/1 Running 0 9m8s
144-
kube-system kube-controller-manager-ip-172-31-18-145 1/1 Running 0 4m8s
145-
kube-system kube-controller-manager-ip-172-31-25-73 1/1 Running 0 21m
146-
kube-system kube-controller-manager-ip-172-31-31-210 1/1 Running 0 8m55s
147-
kube-system kube-proxy-57twm 1/1 Running 0 10m
148-
kube-system kube-proxy-f7pc6 1/1 Running 0 5m24s
149-
kube-system kube-proxy-rj4t5 1/1 Running 0 21m
150-
kube-system kube-scheduler-ip-172-31-18-145 1/1 Running 0 4m15s
151-
kube-system kube-scheduler-ip-172-31-25-73 1/1 Running 0 21m
152-
kube-system kube-scheduler-ip-172-31-31-210 1/1 Running 0 8m48s
153-
kube-system rke2-canal-4x972 2/2 Running 0 10m
154-
kube-system rke2-canal-flh8m 2/2 Running 0 5m24s
155-
kube-system rke2-canal-zfhkr 2/2 Running 0 21m
156-
kube-system rke2-coredns-rke2-coredns-6cd96645d6-cmstq 1/1 Running 0 21m
157-
kube-system rke2-ingress-nginx-controller-54946dd48f-6mp76 1/1 Running 0 20m
158-
kube-system rke2-ingress-nginx-default-backend-5795954f8-p92xx 1/1 Running 0 20m
159-
kube-system rke2-metrics-server-5f9b5757dc-k5sgh 1/1 Running 0 20m
131+
/var/lib/rancher/rke2/bin/kubectl --kubeconfig /etc/rancher/rke2/rke2.yaml get pods -A
132+
NAMESPACE NAME READY STATUS RESTARTS AGE
133+
kube-system cloud-controller-manager-rke2-server-1 1/1 Running 0 2m28s
134+
kube-system cloud-controller-manager-rke2-server-2 1/1 Running 0 61s
135+
kube-system cloud-controller-manager-rke2-server-3 1/1 Running 0 49s
136+
kube-system etcd-rke2-server-1 1/1 Running 0 2m13s
137+
kube-system etcd-rke2-server-2 1/1 Running 0 87s
138+
kube-system etcd-rke2-server-3 1/1 Running 0 56s
139+
kube-system helm-install-rke2-canal-hs6sx 0/1 Completed 0 2m17s
140+
kube-system helm-install-rke2-coredns-xmzm8 0/1 Completed 0 2m17s
141+
kube-system helm-install-rke2-ingress-nginx-flwnl 0/1 Completed 0 2m17s
142+
kube-system helm-install-rke2-metrics-server-7sggn 0/1 Completed 0 2m17s
143+
kube-system kube-apiserver-rke2-server-1 1/1 Running 0 116s
144+
kube-system kube-apiserver-rke2-server-2 1/1 Running 0 66s
145+
kube-system kube-apiserver-rke2-server-3 1/1 Running 0 48s
146+
kube-system kube-controller-manager-rke2-server-1 1/1 Running 0 2m30s
147+
kube-system kube-controller-manager-rke2-server-2 1/1 Running 0 57s
148+
kube-system kube-controller-manager-rke2-server-3 1/1 Running 0 42s
149+
kube-system kube-proxy-rke2-server-1 1/1 Running 0 2m25s
150+
kube-system kube-proxy-rke2-server-2 1/1 Running 0 59s
151+
kube-system kube-proxy-rke2-server-3 1/1 Running 0 85s
152+
kube-system kube-scheduler-rke2-server-1 1/1 Running 0 2m30s
153+
kube-system kube-scheduler-rke2-server-2 1/1 Running 0 57s
154+
kube-system kube-scheduler-rke2-server-3 1/1 Running 0 42s
155+
kube-system rke2-canal-b9lvm 2/2 Running 0 91s
156+
kube-system rke2-canal-khwp2 2/2 Running 0 2m5s
157+
kube-system rke2-canal-swfmq 2/2 Running 0 105s
158+
kube-system rke2-coredns-rke2-coredns-547d5499cb-6tvwb 1/1 Running 0 92s
159+
kube-system rke2-coredns-rke2-coredns-547d5499cb-rdttj 1/1 Running 0 2m8s
160+
kube-system rke2-coredns-rke2-coredns-autoscaler-65c9bb465d-85sq5 1/1 Running 0 2m8s
161+
kube-system rke2-ingress-nginx-controller-69qxc 1/1 Running 0 52s
162+
kube-system rke2-ingress-nginx-controller-7hprp 1/1 Running 0 52s
163+
kube-system rke2-ingress-nginx-controller-x658h 1/1 Running 0 52s
164+
kube-system rke2-metrics-server-6564db4569-vdfkn 1/1 Running 0 66s
160165
```
161166
162167
**Result:** You have confirmed that you can access the cluster with `kubectl` and the RKE2 cluster is running successfully. Now the Rancher management server can be installed on the cluster.
163-
164-
### 5. Configure nginx to be a daemonset
165-
166-
Currently, RKE2 deploys nginx-ingress as a deployment, and that can impact the Rancher deployment so that you cannot use all servers to proxy requests to the Rancher pods.
167-
168-
To rectify that, place the following file in /var/lib/rancher/rke2/server/manifests on any of the server nodes:
169-
170-
```yaml
171-
apiVersion: helm.cattle.io/v1
172-
kind: HelmChartConfig
173-
metadata:
174-
name: rke2-ingress-nginx
175-
namespace: kube-system
176-
spec:
177-
valuesContent: |-
178-
controller:
179-
kind: DaemonSet
180-
daemonset:
181-
useHostPort: true
182-
```

0 commit comments

Comments
 (0)