Challenges by Omkar Shelke

Focused, hands-on DevOps and server-side problems with hints, feedback, and automated solution checks.

Omkar Shelke
Omkar Shelke

Kubernetes enthusiast and certified CKA & CKAD, passionate about building, exploring, and explaining cloud-native technologies. Constantly learning, experimenting, and sharing practical Kubernetes knowledge

Challenge

Use a Kubernetes Job to Test NATS Pub/Sub

A payment service subscribes to payment requests through NATS. Run the checkout team's test script as a Job in the checkout namespace, with the required settings, and make sure the payment request arrives.

Challenge

Fix a Deployment Stuck in ImagePullBackOff

A freshly rolled out Deployment has its Pods stuck in ImagePullBackOff, and the catalog page it serves returns 503. Read what the cluster reports about the failed pulls, find out why the image does not pull, and get the Pods running.

Challenge

Node Is Ready, but Pods Won't Schedule

node-02 is back from a kernel upgrade but still shows Ready,SchedulingDisabled, and the Pods that can only run on it are stuck in Pending. Bring the node back into service and get the workload running, without touching the workload itself.

Challenge

Debug a Pod Stuck at 0/1 Ready Due to a Readiness Probe

A new intern learning about probes wrote a small Pod manifest. The exec command and the application are both correct, but the Pod never becomes Ready because one probe parameter is missing. Find it and add it.

Challenge

Troubleshoot Why the Calendar Todo App Pods Are Stuck in Pending

The production "Calendar Todo" web application has been deployed in the prod namespace but all pods are stuck in Pending. Investigate the cluster, identify why the application cannot run, fix the underlying node issue, and verify the app is serving traffic on NodePort 31777.

Challenge

Resolve ContainerCreating Issue Caused by Missing ConfigMap

A Deployment is stuck with Pods in ContainerCreating state because the required ConfigMap was not created. Fix the issue to make the application accessible.

Challenge

Troubleshoot CrashLoopBackOff Caused by a Missing TLS Secret

A deployment is failing because the application cannot load its TLS certificate. Create the missing secret and mount it into the deployment so the Flask app can serve TLS traffic.