Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
Design Kubernetes clusters for scaling, service discovery, storage, and networking. Plan upgrades and multi-cluster strategies. Use when architecting container infrastructure.
npx claudepluginhub sethdford/claude-skills --plugin architect-infrastructure-designHow this skill is triggered — by the user, by Claude, or both
Slash command
/infrastructure-design:container-orchestrationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Design and operate Kubernetes clusters for scalable, resilient container deployments.
Designs Kubernetes platform architecture, implements GitOps workflows (ArgoCD/Flux), and plans multi-cluster strategy, service mesh, and security patterns.
Plan container orchestration, load balancing, high availability, and scaling. Design deployment topologies for production systems. Use when architecting deployment infrastructure or modernizing deployment practices.
Share bugs, ideas, or general feedback.
Design and operate Kubernetes clusters for scalable, resilient container deployments.
You are designing Kubernetes infrastructure. Plan cluster architecture, scaling policies, storage, networking, and operations. Read workload characteristics, scale requirements, and team Kubernetes maturity.
Based on Kubernetes best practices (CNCF, Google, AWS EKS):
Design Cluster Topology: Single cluster (simpler) or multi-cluster (HA, isolation)? Multi-AZ for resilience. Master nodes (API server, etcd) managed by cloud provider (EKS, GKE).
Plan Node Sizing: How many nodes for peak load? Large nodes (fewer, simpler) vs small nodes (more flexible). Use auto-scaling to handle traffic spikes.
Configure Storage: Stateless apps: no storage needed. Stateful: PersistentVolumes for databases, caches. Use managed databases (RDS) for data, K8s for cache (Redis).
Set Up Networking: Calico or Weave for container networking. Service mesh (Istio) for traffic management. Ingress controller for external traffic. Network policies for security.
Plan Operations: Helm for templating deployments. Flux or ArgoCD for GitOps-driven deployments. Monitoring (Prometheus), logging (ELK), tracing (Jaeger). Regular upgrades.