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
killercoda - A hands on learning platform to master Kubernetes, Linux, and DevOps tools.
Perfect for certifications like CKA, CKAD, CKS, LFCS, and ICA.
Right in your browser. No setup needed, just start learning.
Gain hands on skills for real world DevOps challenges.
🧠 USE CASE
Kubernetes Autoscaling - HPA vs VPA vs KEDA
Which type of autoscaling should I use for my workload?
Can I scale based on message queues or external triggers?
What happens if I combine multiple autoscaling strategies?
No seasoned Kubernetes professional can skip these questions in their career.
Since there is already tons of information available on how to set up autoscaling, let’s not go there.
For someone yet to know, you can refer to the Autoscaling Workloads guide here.
And I have tried to simplify the behind the scenes as a self-explanatory illustration below:
Despite being powerful, Kubernetes autoscaling has its pitfalls, understanding how and when to use each autoscaler is critical.
1. Horizontal Pod Autoscaler (HPA)
HPA is the default choice for scaling Kubernetes workloads horizontally by adding or removing pods based on resource utilization or custom metrics.
How HPA Works:
Continuously monitors metrics like CPU, memory, or custom metrics (e.g., request rates).
Adjusts the number of pod replicas in a deployment based on predefined thresholds.
Formula:
desiredReplicas = ceil(currentReplicas * (currentMetricValue / targetValue)).
2. Vertical Pod Autoscaler (VPA)
VPA optimizes pod resource requests (CPU and memory) by learning from historical and real-time usage patterns.
How VPA Works:
Analyzes resource utilization and suggests or directly applies changes to resource requests/limits.
Modes:
Auto: Automatically applies resource recommendations.
Initial: Sets resource requests at pod creation only.
Off: Provides recommendations without applying changes.
3. Kubernetes Event-Driven Autoscaling (KEDA)
KEDA extends autoscaling to handle event-driven workloads by scaling deployments based on external triggers like message queues, HTTP requests, or custom metrics.
How KEDA Works:
Integrates with external systems (e.g., Kafka, RabbitMQ) to fetch metrics and decide scaling.
Uses
ScaledObjectsto define scaling rules and event sources.
For many workloads, a hybrid approach works best:
HPA + VPA: Use HPA to scale pods based on CPU/memory usage while VPA adjusts pod resource requests for efficient utilization.
HPA + KEDA: Use HPA for resource-based scaling and KEDA for event-driven scaling.
HPA + VPA + KEDA: Combine all three for workloads that are both resource-intensive and event-driven, ensuring cost efficiency and performance.
You may even like:
Looking to promote your company, product, service, or event to 49,000+ TechOps Professionals? Let's work together.
