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.
AI-skilled professionals are earning up to 56% higher wages.
Companies are rewarding engineers who can build with AI.
THE CODE - Learn how to code faster with AI in 5 mins a day.
Loved by 350k+ devs, engineers at Meta, Google, OpenAI, and more.
Somehow, it’s free - Sign up to get The Ultimate Claude Code Guide + 200 Free Engineering resources.
👀 Remote Jobs
Railway is hiring a Senior Infra Engineer: Platform
Remote Location: Worldwide
Social Discovery Group is hiring a Site Reliability Engineer
Remote Location: Worldwide
📚 Resources
If you’re not a subscriber, here’s what you missed last week.
To receive all the full articles and support TechOps Examples, consider subscribing:
🛠 TOOL OF THE DAY
kubetail - Real time logging dashboard for Kubernetes. View logs in a terminal or a browser.
Run anywhere - desktop, cluster, docker.
🧠 USE CASE
Kubernetes Resource Management Explained
Kubernetes clusters are shared infrastructure. Without guardrails, a single team running a poorly configured batch job can consume every CPU and memory resource on every node, starving every other team's workloads. Production services go down not because of a bug in their own code but because a neighbouring namespace consumed everything.
A ResourceQuota sets hard limits on how much CPU, memory, and other resources a namespace can use. It prevents teams from overusing shared cluster resources and ensures fair access across environments.
How Kubernetes Applies Resource Quotas
The API server receives the pod request and runs admission checks.
The ResourceQuota plugin verifies if CPU and memory stay within namespace limits.
If over quota, the request is denied before scheduling.
If valid, usage is updated and the pod is linked to a service account.
The final state is saved in etcd for tracking and enforcement.
Requests and Limits - What They Really Mean
Containers run inside pods, and every container consumes compute resources. But you don’t just let them use as much as they want. You tell Kubernetes two things:
Request: This is the minimum resource the container is guaranteed. Kubernetes uses this during scheduling.
Limit: This is the upper cap. A container cannot exceed this.
Think of it like booking a hotel room. The "request" is the space you block ahead of time. The "limit" is the maximum you’re allowed to use. You can’t burst beyond it.
In case of CPU:
If usage exceeds the request but stays under the limit, the container runs, but may get throttled if the node is under pressure.
If it goes beyond the limit, it gets throttled instantly.
For memory:
If it uses more than requested, it's allowed, but if it crosses the limit, the pod is killed with an OOM (Out Of Memory) error.
A real world pod manifest look like this:
How Quotas Connect to Pod level Resource Specs
ResourceQuota operates at the namespace aggregate level but connects directly to the resource requests and limits on individual pods and containers.
The ResourceQuota admission plugin adds up the requests and limits across all containers in all running pods in the namespace and compares the sum against the quota whenever a new pod is submitted.
This creates a dependency that catches many engineers off guard. When a namespace has a ResourceQuota defined, every pod submitted to that namespace must specify resource requests and limits on every container. A pod without them is rejected immediately.
This is intentional. A quota tracking total CPU requests cannot function correctly if some pods have no CPU requests because those pods consume unmeasured resources and the accounting breaks. This is why LimitRange is commonly paired with ResourceQuota. LimitRange injects default requests and limits into pods that do not specify them, so developers do not need to add resource specs manually on every pod while the quota enforcement stays complete and accurate.
THE CODE - Learn how to code faster with AI in 5 mins a day. Loved by 350k+ devs, engineers at Meta, Google, OpenAI, and more.
🔴 Get my DevOps & Kubernetes ebooks! (free for Premium Club and Personal Tier newsletter subscribers)
Looking to promote your company, product, service, or event to 50,000+ DevOps and Cloud Professionals? Let's work together.
