305-998-7702 | 415-800-2922 info@rx-m.com

Practice Drill

Run the following command. This command will start a pod that will not run: kubectl run –restart Never –image redis:0.2 redispod Retrieve the events associated with this pod (listed in any order) and write them to a file: /tmp/troubleshooting-answer.txt...

Troubleshoot Networking

Every pod running in a Kubernetes cluster must have its own IP address. Pods receive their unique IPs from the cluster Container Network Interface (CNI) plugin. In order to properly use a CNI plugin, each Kubelet must be configured to expect CNI plugins in their...

Troubleshoot Worker Node Failure

A node that runs pods in a Kubernetes cluster is represented by a kubelet. Each kubelet requires a container runtime (like Docker) to run containers. Since the kubelet and container runtime run as system agents, you must use host-level tools...

Troubleshoot Control Plane Failure

Control plane components like the kube-apiserver, kube-scheduler, etcd, and kube-controllermanager all run in static pods in a kubeadm-bootstrapped cluster. Control plane components manifests are found in the master node’s kubelet static path directory, the default...

Troubleshoot Application Failure

Applications running under Kubernetes run in containers within pods. There are several ways to troubleshoot application failures: Reading the application container’s logs using kubectl logsViewing events associated with the pod using kubectl...