TechOps Examples
Hey — It's Govardhana MK 👋
Welcome to another technical edition.
Every Tuesday – You’ll receive a free edition with a byte-size use case, remote job opportunities, top news, tools, and articles.
Every Thursday and Saturday – You’ll receive a special edition with a deep dive use case, remote job opportunities and articles.
Top engineers at Anthropic and OpenAI say AI now writes 100% of their code.
If you're not using AI, you're spending 40 hours doing what they do in 4.
These 100+ Claude Code hacks fix that and help you ship 10x faster.
Sign up for The Code and get:
100+ Claude Code hacks used by top engineers — free
The Code newsletter — learn the latest AI tools, tips, and skills to code faster with AI in 5 minutes a day
🛠 TOOL OF THE DAY
Litmus - helps SREs and developers practice chaos engineering in a Cloud-native way.
Multi Tenant for K8s
Chaos experiments are chained in sequence or parallel to build a scenario.
Litmus exports Prometheus metrics to quantify the impact of chaos on applications or infrastructure.
🧠 USE CASE
How a Pod is Deleted - Behind the Scenes Breakdown
When we run kubectl delete pod , the confirmation message pops up saying the pod is deleted(if all good)
$ kubectl delete pod techops-pod
pod "techops-pod" deletedWondered, what happens behind the scenes?
Before diving into pod deletion behind the scenes, you should know the basics.
SIGTERM: Requests a graceful shutdown, allowing the program to finish tasks and clean up. In Kubernetes, pods get time to exit cleanly.
SIGKILL: Forces an immediate stop, with no cleanup. If a pod doesn't shut down in time after SIGTERM, Kubernetes sends SIGKILL to terminate it.
In short,
SIGTERM allows for cleanup.
SIGKILL stops everything instantly.
Pod Deletion - Behind the Scenes:
Pod deletion flow
kubectl delete pod: Triggers the API Server to update ETCD with
deletionTimestampanddeletionGracePeriodSeconds, marking the pod as Terminating.API Server → Kubelet: Notifies the Kubelet of the pod’s termination.
Endpoint Controller: Removes the pod from active service endpoints, stopping any traffic from reaching the pod.
PreStop Hook (if configured): Before sending SIGTERM, the Kubelet runs the PreStop Hook. This allows the pod to perform custom tasks (e.g., closing connections) during shutdown.
SIGTERM: Kubelet sends SIGTERM, initiating a graceful shutdown. The pod is given the
deletionGracePeriodSeconds(default 30s) to cleanly exit.Graceful Shutdown: During the grace period, the pod handles any ongoing tasks, such as completing requests or saving data, before it fully stops.
SIGKILL: If the pod doesn't terminate within the grace period, SIGKILL is sent, forcing immediate shutdown.
Pod Deleted: The API Server updates ETCD, marking the pod as deleted. Components like Kube-Proxy, Ingress, and others remove all references to the pod.
Here are some common signals for your knowledge (though out of context):
SIGHUP: Hangup signal
SIGINT: Interrupt signal (triggered by Ctrl+C)
SIGQUIT: Quit signal
SIGSTOP: Stop the process (cannot be caught or ignored)
I hope this was helpful in your learning journey.
You may even like:
Looking to promote your company, product, service, or event to 50,000+ TechOps Professionals? Let's work together.
