Quality improvement.

This commit is contained in:
savagebidoof 2023-08-01 20:06:33 +02:00
parent e8729db48f
commit 1454839692

View File

@ -1752,33 +1752,40 @@ PLAY RECAP *********************************************************************
<span style="color:#CC3980">slave02.filter.home</span> : <span style="color:#7F3FBF">ok=12 </span> <span style="color:#CC3980">changed=23 </span> unreachable=0 failed=0 <span style="color:#7f7fff">skipped=12 </span> rescued=0 ignored=0
</pre>
#### Check cluster status
First I will copy the kubeconfig file to a place of my own.
```shell
cp ksetup/Exported/kubeconfig.conf ~/kubeconfig.conf -v
```
```text
'ksetup/Exported/kubeconfig.conf' -> '/home/savagebidoof/kubeconfig.conf'
```
Pods are deployed correctly
```shell
kubectl get pods --kubeconfig ksetup/Exported/kubeconfig.conf -A
kubectl get pods --kubeconfig ~/kubeconfig.conf -A -owide
```
```text
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system calico-kube-controllers-85578c44bf-k5sgl 1/1 Running 1 51m
kube-system calico-node-2tn68 1/1 Running 1 (10m ago) 51m
kube-system calico-node-hksmv 1/1 Running 1 (10m ago) 12m
kube-system coredns-5d78c9869d-tblcq 1/1 Running 1 (10m ago) 71m
kube-system coredns-5d78c9869d-vmx8q 1/1 Running 1 (10m ago) 71m
kube-system etcd-pi4.filter.home 1/1 Running 1 (10m ago) 71m
kube-system kube-apiserver-pi4.filter.home 1/1 Running 1 (10m ago) 71m
kube-system kube-controller-manager-pi4.filter.home 1/1 Running 1 (10m ago) 71m
kube-system kube-proxy-cqvws 1/1 Running 1 (10m ago) 12m
kube-system kube-proxy-vwlkx 1/1 Running 1 (10m ago) 71m
kube-system kube-scheduler-pi4.filter.home 1/1 Running 1 (10m ago) 71m
metallb-system controller-595f88d88f-q87gr 1/1 Running 2 51m
metallb-system speaker-5zptn 1/1 Running 2 (8m29s ago) 50m
metallb-system speaker-whw4n 1/1 Running 2 (8m22s ago) 12m
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
kube-system calico-kube-controllers-85578c44bf-k5sgl 1/1 Running 1 65m 172.16.86.72 pi4.filter.home <none> <none>
kube-system calico-node-2tn68 1/1 Running 1 (24m ago) 65m 192.168.1.9 pi4.filter.home <none> <none>
kube-system calico-node-hksmv 1/1 Running 1 (24m ago) 26m 192.168.1.11 slave02.filter.home <none> <none>
kube-system coredns-5d78c9869d-tblcq 1/1 Running 1 (24m ago) 85m 172.16.86.70 pi4.filter.home <none> <none>
kube-system coredns-5d78c9869d-vmx8q 1/1 Running 1 (24m ago) 85m 172.16.86.69 pi4.filter.home <none> <none>
kube-system etcd-pi4.filter.home 1/1 Running 1 (24m ago) 85m 192.168.1.9 pi4.filter.home <none> <none>
kube-system kube-apiserver-pi4.filter.home 1/1 Running 1 (24m ago) 85m 192.168.1.9 pi4.filter.home <none> <none>
kube-system kube-controller-manager-pi4.filter.home 1/1 Running 1 (24m ago) 85m 192.168.1.9 pi4.filter.home <none> <none>
kube-system kube-proxy-cqvws 1/1 Running 1 (24m ago) 26m 192.168.1.11 slave02.filter.home <none> <none>
kube-system kube-proxy-vwlkx 1/1 Running 1 (24m ago) 85m 192.168.1.9 pi4.filter.home <none> <none>
kube-system kube-scheduler-pi4.filter.home 1/1 Running 1 (24m ago) 85m 192.168.1.9 pi4.filter.home <none> <none>
metallb-system controller-595f88d88f-q87gr 1/1 Running 2 65m 172.16.86.71 pi4.filter.home <none> <none>
metallb-system speaker-5zptn 1/1 Running 2 (22m ago) 64m 192.168.1.9 pi4.filter.home <none> <none>
metallb-system speaker-whw4n 1/1 Running 2 (22m ago) 26m 192.168.1.11 slave02.filter.home <none> <none>
```