K8s Deployment Verification

To simplify managing the K8s cluster from the Jump Host, set up kubectl with bash auto-completion.

1. Copy kubectl and the kubeconfig file from master1 to the Jump Host:

   Jump Node Console

   Collapse Source

   Copy

   Copied!

               
   
               
   ## Connect to master1
   depuser@jump:~$ ssh master1
   depuser@master1:~$ cp /usr/local/bin/kubectl /tmp/
   depuser@master1:~$ sudo cp /root/.kube/config /tmp/kube-config
   depuser@master1:~$ sudo chmod 644 /tmp/kube-config
           

2. In another terminal tab, copy the files to the Jump Host:

   Jump Node Console

   Collapse Source

   Copy

   Copied!

               
   
               
   depuser@jump:~$ scp master1:/tmp/kubectl /tmp/
   depuser@jump:~$ sudo chown root:root /tmp/kubectl
   depuser@jump:~$ sudo mv /tmp/kubectl /usr/local/bin/
   depuser@jump:~$ mkdir -p ~/.kube
   depuser@jump:~$ scp master1:/tmp/kube-config ~/.kube/config
   depuser@jump:~$ chmod 600 ~/.kube/config
           

3. Enable bash auto-completion for kubectl:

   1. Verify if bash-completion is installed:

      Jump Node Console

      Collapse Source

      Copy

      Copied!

                  
      
                  
      depuser@jump:~$ type _init_completion
              

      If installed, the output includes:

      Jump Node Console

      Collapse Source

      Copy

      Copied!

                  
      
                  
      _init_completion is a function
              

   2. If not installed, install it:

      Jump Node Console

      Collapse Source

      Copy

      Copied!

                  
      
                  
      depuser@jump:~$ sudo apt install -y bash-completion
              

   3. Set up the kubectl completion script:

      Jump Node Console

      Collapse Source

      Copy

      Copied!

                  
      
                  
      depuser@jump:~$ kubectl completion bash | sudo tee /etc/bash_completion.d/kubectl > /dev/null
      depuser@jump:~$ bash
              

4. Check the status of the nodes in the cluster:

   Jump Node Console

   Collapse Source

   Copy

   Copied!

               
   
               
   depuser@jump:~$ kubectl get nodes
           

   Expected output:

   Jump Node Console

   Collapse Source

   Copy

   Copied!

               
   
               
   NAME      STATUS     ROLES           AGE   VERSION
   master1   Ready    control-plane   8m7s    v1.30.4
   master2   Ready    control-plane   7m13s   v1.30.4
   master3   Ready    control-plane   6m40s   v1.30.4
           

5. Check the pods in all namespaces:

   Jump Node Console

   Collapse Source

   Copy

   Copied!

               
   
               
   depuser@jump:~$ kubectl get pods -A
           

   Expected output:

   Jump Node Console

   Collapse Source

   Copy

   Copied!

               
   
               
   [depuser@setup5-jump ~]$ kubectl get pods -A
   NAMESPACE     NAME                              READY   STATUS    RESTARTS   AGE
   kube-system   coredns-776bb9db5d-2st6b          1/1     Running   0          5m58s
   kube-system   coredns-776bb9db5d-kbklh          1/1     Running   0          5m53s
   kube-system   dns-autoscaler-6ffb84bd6-cp466    1/1     Running   0          5m54s
   kube-system   kube-apiserver-master1            1/1     Running   0          8m35s
   kube-system   kube-apiserver-master2            1/1     Running   0          7m44s
   kube-system   kube-apiserver-master3            1/1     Running   0          7m10s
   kube-system   kube-controller-manager-master1   1/1     Running   1          8m35s
   kube-system   kube-controller-manager-master2   1/1     Running   1          7m44s
   kube-system   kube-controller-manager-master3   1/1     Running   1          7m10s
   kube-system   kube-flannel-8r2dd                1/1     Running   0          6m22s
   kube-system   kube-flannel-sq88x                1/1     Running   0          6m22s
   kube-system   kube-flannel-xf9mn                1/1     Running   0          6m23s
   kube-system   kube-proxy-4v7hn                  1/1     Running   0          8m21s
   kube-system   kube-proxy-6cdjc                  1/1     Running   0          7m14s
   kube-system   kube-proxy-tm2j4                  1/1     Running   0          7m47s
   kube-system   kube-scheduler-master1            1/1     Running   1          8m36s
   kube-system   kube-scheduler-master2            1/1     Running   1          7m45s
   kube-system   kube-scheduler-master3            1/1     Running   1          7m10s
   kube-system   kube-vip-master1                  1/1     Running   0          8m35s
   kube-system   kube-vip-master2                  1/1     Running   0          7m45s
   kube-system   kube-vip-master3                  1/1     Running   0          7m10s