kubernetes-production

Configure production Kubernetes workloads with autoscaling, security, and observability.

5|1|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/roanbrasil/engineer-grade-agent-skills --skill kubernetes-production
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kubernetes-production
Source: https://github.com/roanbrasil/engineer-grade-agent-skills/tree/main/skills/kubernetes-production
Command: npx skills add https://github.com/roanbrasil/engineer-grade-agent-skills --skill kubernetes-production

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of costly production outages, security breaches, and performance bottlenecks caused by misconfigured Kubernetes workloads, autoscaling policies, and networking rules, which are common pitfalls for teams running containerized services at scale.

Core Features & Use Cases

  • Workload Design & Resource Management: Choose the correct controller (Deployment, StatefulSet, DaemonSet) for your use case, configure resource requests/limits and QoS classes to avoid eviction and throttling, and implement init containers and sidecars for setup and cross-cutting concerns.
  • Autoscaling & Availability: Configure HPA, VPA, KEDA, and Cluster Autoscaler to handle variable load, set up PodDisruptionBudgets, pod anti-affinity, and probes to ensure high availability during node drains and rolling upgrades.
  • Security & Observability: Harden workloads with RBAC, pod security contexts, and NetworkPolicies, set up structured logging and Prometheus metrics, and use essential kubectl commands for fast incident response.
  • Use Case: For a stateless e-commerce API, use this Skill to configure a Deployment with Guaranteed QoS, HPA scaling on CPU and request rate, pod anti-affinity across availability zones, and default-deny NetworkPolicies to achieve 99.95% availability and prevent lateral movement from compromised pods.

Quick Start

Use the kubernetes-production skill to configure a production-ready Deployment for your stateless API service with appropriate resource requests, HPA autoscaling rules, and NetworkPolicies to restrict traffic to only the ingress controller and database.

Frequently Asked Questions about kubernetes-production

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Kubernetes autoscaling for variable traffic loads?

Configure Kubernetes autoscaling by setting up HPA, VPA, KEDA, and Cluster Autoscaler to handle variable traffic loads. This ensures your workloads scale dynamically based on CPU utilization and request rates, maintaining availability during sudden spikes without manual intervention.

What is the best way to prevent pod eviction in Kubernetes production environments?

Prevent pod eviction in Kubernetes production by configuring resource requests, limits, and QoS classes appropriately. Setting Guaranteed QoS for critical workloads ensures pods have reserved compute resources, protecting them from eviction during node resource pressure.

How does pod anti-affinity improve availability during node drains?

Pod anti-affinity improves availability during node drains by distributing replicas across multiple availability zones. Combined with PodDisruptionBudgets, it ensures a minimum number of pods remain running, preventing total service outage during rolling upgrades or maintenance.

Can I use NetworkPolicies to restrict traffic to a stateless API?

Yes, you can use NetworkPolicies to restrict traffic to a stateless API by implementing default-deny rules. This limits ingress traffic to only the ingress controller and database, preventing lateral movement from compromised pods and hardening security.

When do I need a StatefulSet instead of a Deployment for Kubernetes workloads?

You need a StatefulSet instead of a Deployment for Kubernetes workloads requiring stable network identities and persistent storage. Deployments are ideal for stateless services, while StatefulSets manage stateful applications and event-driven workloads.

What observability pipelines are required for Kubernetes incident response?

Kubernetes incident response requires observability pipelines using structured logging and Prometheus metrics. These pipelines provide visibility into workload health, allowing teams to use essential kubectl commands for fast troubleshooting and compliance monitoring.