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 will include:

      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:

   Note

   Nodes will be in the NotReady state because the deployment did not include CNI components.

   Jump Node Console

   Collapse Source

   Copy

   Copied!

               
   
               
   NAME      STATUS     ROLES           AGE   VERSION
   master1   NotReady   control-plane   16m   v1.30.4
   master2   NotReady   control-plane   15m   v1.30.4
   master3   NotReady   control-plane   14m   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:

   Note

   coredns and dns-autoscaler pods will be in the Pending state due to the absence of CNI components.

   Jump Node Console

   Collapse Source

   Copy

   Copied!

               
   
               
   NAMESPACE     NAME                              READY   STATUS    RESTARTS   AGE
   kube-system   coredns-776bb9db5d-9bjhd          0/1     Pending   0          14m
   kube-system   dns-autoscaler-6ffb84bd6-8jnjj    0/1     Pending   0          14m
   kube-system   kube-apiserver-master1            1/1     Running   0          16m
   kube-system   kube-apiserver-master2            1/1     Running   0          15m
   kube-system   kube-apiserver-master3            1/1     Running   0          14m
   kube-system   kube-controller-manager-master1   1/1     Running   1          16m
   kube-system   kube-controller-manager-master2   1/1     Running   1          15m
   kube-system   kube-controller-manager-master3   1/1     Running   1          14m
   kube-system   kube-scheduler-master1            1/1     Running   1          16m
   kube-system   kube-scheduler-master2            1/1     Running   1          15m
   kube-system   kube-scheduler-master3            1/1     Running   1          14m
   kube-system   kube-vip-master1                  1/1     Running   0          16m
   kube-system   kube-vip-master2                  1/1     Running   0          14m
   kube-system   kube-vip-master3                  1/1     Running   0          14m