Kubernetes ConfigMap Update Fails to Refresh Env Vars

See your Kubernetes, not just debug it. With Netpin Topology: • Visualize your cluster in real-time • Check describe, logs, and resources in one place • Quickly spot issues and dependencies Less switching. More clarity ⚡ #Netpin #Kubernetes #DevOps #K8s #Observability #PlatformEngineering

Most Kubernetes issues aren’t about lack of data — they’re about lack of visibility. We’ve been building Netpin with a simple belief: you should be able to see your infrastructure, not just query it. Topology is a step in that direction — bringing together visualization, logs, describe, and resource insights in one place. No context switching, no guesswork. Still early, but excited about where this is going. #Netpin #Kubernetes #DevOps #K8s #Observability #PlatformEngineering

Most deployment issues aren’t caused by containers They’re caused by not understanding the flow. In OpenShift, nothing works in isolation. Every request follows a path: 𝐔𝐬𝐞𝐫 → 𝐑𝐨𝐮𝐭𝐞 → 𝐒𝐞𝐫𝐯𝐢𝐜𝐞 → 𝐏𝐨𝐝𝐬 → 𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫𝐬 Each layer has a purpose: - Route exposes the application - Service directs traffic - Pods handle scaling - Containers run the code Individually, these are simple. But together, they determine whether your application actually works in the real world. That’s the shift: - You’re not just deploying a container - You’re defining how traffic moves through your system Once that clicks, OpenShift becomes far more predictable. I’ve broken this into a single visual (attached) to show the flow #OpenShift #Kubernetes #DevOps

🚀 Hands-on with Kubernetes Liveness Probe Implemented a liveness probe using the exec method and simulated failure by removing /tmp/healthy. Kubernetes detected the issue and restarted the container automatically. Liveness probe ensures containers don’t stay in a broken state and helps maintain self-healing systems. However, incorrect configuration can lead to unnecessary restarts. Ashutosh S. Bhakare Ajinath Kale #Kubernetes #DevOps #Containers

ReplicaSets and Deployments in Kubernetes aren't the same thing❌. A ReplicaSet ensures a specific number of pod replicas are running. That's it. It's a primitive controller focused on maintaining count. A Deployment is higher-level. It manages ReplicaSets for you and adds 𝗿𝗼𝗹𝗹𝗼𝘂𝘁 𝗰𝗮𝗽𝗮𝗯𝗶𝗹𝗶𝘁𝗶𝗲𝘀: rolling updates, rollbacks, version history. When you create a Deployment, Kubernetes automatically creates a ReplicaSet underneath. The Deployment orchestrates changes by creating new ReplicaSets and scaling down old ones. The key difference: ReplicaSets are stateless managers. 𝗗𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁𝘀 𝗮𝗿𝗲 𝘀𝘁𝗮𝘁𝗲𝗳𝘂𝗹 𝗼𝗿𝗰𝗵𝗲𝘀𝘁𝗿𝗮𝘁𝗼𝗿𝘀. You rarely create ReplicaSets directly. Use Deployments for almost everything. They give you the replica management plus deployment strategy. The only time you'd use a bare ReplicaSet? When you need simple pod replication without any update mechanics. #Kubernetes #DevOps #CloudNative #ContainerOrchestration

Day 44 of #100DaysOfDevOps I deployed a Kubernetes pod, got the YAML "right" — and still failed the task. We needed a pod that prints environment variables on startup — GREETING, COMPANY, and GROUP — using a bash image with a one-shot command and restartPolicy: Never. Simple enough. I wrote the manifest, triple-checked the env values, the command syntax, the restart policy. Looked clean. It wasn't. The pod name was print-envars-greeting. And I'd used the same name for the container too — out of habit. The requirement said the container name should be print-env-container. One field, buried in spec, completely overlooked. Changed it, reapplied, done. spec: restartPolicy: Never containers: - name: print-env-container image: bash command: ["/bin/sh", "-c", 'echo "$GREETING $COMPANY $GROUP"'] env: - name: GREETING value: "Welcome to" - name: COMPANY value: "xFusionCorp" - name: GROUP value: "Group" Kubernetes doesn't care that your logic is right. It cares that your spec matches exactly. In real clusters, a wrong container name breaks log queries, metric scraping, and sidecar injection — silent failures that surface at the worst time. Read the requirements like a contract. Every field is a clause. #Kubernetes #DevOps #KodeKloud #CloudEngineering #LearningInPublic

CrashLoopBackOff is one of the most common things you'll debug in Kubernetes. The pod keeps restarting. The trick is always the same — kubectl logs --previous shows you what happened before the last crash. In this case: missing config file. Config never mounted. Pod never starts. These are the things you only learn by doing. kubernetestrainer.com #Kubernetes #DevOps #CKA #kubectl

"It runs on my machine" doesn't help when production goes down at 3 AM. A robust backend is only as good as the infrastructure it runs on. At Pyrvex, we treat Kubernetes not just as a host, but as a core part of our application architecture. I just published a new piece on how we harden K8s clusters for mission-critical workloads: 🛡️ Zero-downtime deployment strategies that actually work 🛡️ Graceful degradation when dependent services fail 🛡️ Why observability needs to be baked into your deployment pipeline Read the full breakdown here: [Link] How is your team handling K8s deployments right now? GitOps? Helm? Let me know below. #kubernetes #devops #sre #cloudnative

Every kubectl apply kicks off a precise sequence across the Kubernetes control plane, API Server validates and stores your desired state, the Controller Manager builds the object chain, the Scheduler assigns pods to nodes, and Kubelet brings containers to life. Understanding this flow transforms how you debug. Kubernetes isn't magic, it's a reconciliation loop you can reason about. Swipe through to trace the full path from manifest to running pod. #kubernetes #devops #cloudnative #kubectl #cloudpros

Week 10 of our Community Edition testimonials. This week we have two reviews from engineers using Gomboc for Terraform code review in their day to day workflows. What keeps coming up across reviews is the same thing: the VS Code integration removes the friction of adopting a new security tool. It fits where engineers already work, so security stops being an extra step and starts being part of how code gets written. When catching and fixing issues happens before code moves further down the pipeline, the whole team moves faster. Community Edition is free to try on your own projects. #IaC #DevOps #Terraform #CloudSecurity #PlatformEngineering