Skip to main content
DevOps Insightsguides & answers

Articles

All Articles

34 articles found

Diagram: a Deployment owns a ReplicaSet that keeps three Pods running on nodes, with a Service selecting them by label.
Featured

Kubernetes 101: The One Idea, Then the Nouns

Kubernetes explained through the control loop under Pods, Deployments and Services, so you can predict what the cluster will do, not just name its parts. Most introductions stop at the nouns.

Neeraj Jha·7 min read
Diagram of How an upgrade breaks every plan: 1. Provider upgrade, 2. Identity support changes, 3. Existing resources read, 4. Every plan fails, 5. Next release or a pin.
3 min
TerraformIntermediateNew

Terraform Identity Errors After a Provider Upgrade

Missing Resource Identity After Read and Unexpected Identity Change usually start right after a provider upgrade. Why they are provider bugs, and the upgrade-or-pin fix that clears them.

#Terraform#AWS

Neeraj Jha

Diagram of Reading the memory curve: 1. Flat, near the limit, 2. Raise the limit, 3. Steady climb, regular kills, 4. Fix the code, 5. Fine, then one big request, 6. Size for the peak.
3 min
KubernetesIntermediateNew

OOMKilled and Exit Code 137: Limit, Leak or Spike?

OOMKilled means the kernel killed a Kubernetes container for using too much memory. How to tell a low limit from a leak or a one-off spike before you raise anything.

#Kubernetes#troubleshooting

Neeraj Jha

Diagram of Which push failure is yours?: 1. Read the error, 2. blob unknown, image digest, 3. Fix one, 4. timeout awaiting headers, 5. Fix two.
3 min
ContainersIntermediateNew

docker push Failing Since Docker 29.7? Two Causes

Since Docker 29.7, docker push can fail with blob unknown to registry on GitLab or with timeout awaiting response headers on slow registries. How to tell which one you have, and what fixes each.

#Docker#CI/CD

Neeraj Jha

Diagram of One turn of the loop: 1. Container starts, 2. It exits, 3. Kubernetes restarts it, 4. Back-off grows, 5. You read the previous run.
3 min
KubernetesBeginnerNew

CrashLoopBackOff: Find the Cause in Three Commands

CrashLoopBackOff means a Kubernetes container keeps exiting and being restarted. Read the previous container's logs, its exit reason and the pod events, and the cause is usually on screen.

#Kubernetes#troubleshooting

Neeraj Jha

Stay ahead in DevOps

Get tutorials, guides, and insights delivered to your inbox. No spam.

Get new posts by email

Subscribe to get an email when a new blog post is published. Skip anytime.

No spam, unsubscribe anytime.

Diagram of How one lowercase letter fails an apply: 1. Plan, 2. Apply, 3. Provider returns, 4. Terraform compares, 5. Error, object tainted.
3 min
TerraformIntermediateNew

Provider Produced Inconsistent Result After Apply, Explained

Provider produced inconsistent result after apply means the API rewrote a value you sent. How to read the was and but now values, fix the configuration, and avoid the tainted resource it leaves behind.

#Terraform

Neeraj Jha

Diagram of Why a 9 GB build dies at 6 GB: 1. Job starts on ubuntu-26.04, 2. Build writes temp files, 3. Quota reached, 4. disk quota exceeded, 5. Fix applied.
3 min
CI/CDIntermediateNew

Ubuntu 26.04 Puts /tmp in RAM: Big CI Builds Run Out

Ubuntu 26.04 mounts /tmp as a RAM disk with a per-user quota, so large builds fail with disk quota exceeded on the ubuntu-26.04 runner. How to check your job and the two-line fix.

#GitHub Actions#Linux#CI/CD

Neeraj Jha

Diagram of Will pip install here?: 1. You run pip install, 2. Inside a venv?, 3. Marker file present?, 4. pip.conf override?, 5. Refused.
3 min
ScriptingBeginnerNew

pip Says externally-managed-environment: What to Do

Why pip install now fails with externally-managed-environment on Ubuntu 24.04, Debian 12 and Homebrew, and the three fixes that work: a venv, pipx, or apt. Plus why it passes in GitHub Actions and fails in docker build.

#Python#Docker#Linux

Neeraj Jha

Diagram of One request, two controllers: 1. Request arrives, 2. Ingress NGINX matching, 3. Gateway API matching, 4. No match, 5. 404.
3 min
DevOpsIntermediateNew

Leaving Ingress NGINX? Five Things That Will Quietly Return 404

Ingress NGINX was retired in March 2026, and moving the same rules to Gateway API can break routes that worked for years. Five behaviours from the Kubernetes project's own write-up, in plain language, with a check to run before you switch.

#Kubernetes#Nginx

Neeraj Jha

Diagram of From cron line to running job: 1. Your cron line, 2. Default branch only, 3. The queue, 4. Delay or drop, 5. Still enabled?, 6. Your job runs.
3 min
CI/CDBeginnerNew

Why Your GitHub Actions Cron Runs Late, or Not at All

Why a GitHub Actions scheduled workflow runs late or not at all: at most every five minutes, delays at busy times, default branch only, and UTC by default. Plus the 60-day switch-off in public repositories, and how to stop being surprised.

#GitHub Actions#CI/CD

Neeraj Jha