azure-kubernetes
Azure Kubernetes guides you through planning and provisioning AKS clusters for production, distinguishing critical Day-0 decisions (networking, API server access) from post-creation features. It covers SKU selection, pod IP models, security with Entra ID and policies, observability via Managed Prometheus, upgrade strategies, and cost optimization including Spot nodes.
Azure Kubernetes helps you plan and configure production-ready AKS clusters with Day-0 decisions on networking and security.
AI-generated summary based on this skill's SKILL.md
Install
microsoft/azure-skills/azure-kubernetes · repository language: Python
git clone https://github.com/microsoft/azure-skills
cp -r azure-skills/skills/azure-kubernetes ~/.claude/skills/azure-kubernetesnpx skillfed install microsoft/azure-skills/azure-kubernetesFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I create an AKS cluster?
Azure Kubernetes helps you plan and create production-ready AKS clusters by guiding Day-0 decisions before provisioning begins. Key steps include choosing between Automatic and Standard SKUs, selecting your pod IP model (Azure CNI Overlay or VNet-routable), configuring API server access (public or private), setting up networking with appropriate subnets, and enabling security features like Entra ID integration. The skill emphasizes that certain decisions—like networking topology and API server visibility—cannot be changed after cluster creation, so planning upfront is critical.
What is the difference between AKS Automatic and Standard SKU?
Azure Kubernetes explains that AKS Automatic and Standard are two distinct SKU options for cluster management. Automatic SKU provides a more managed experience with simplified defaults and automated tuning, while Standard SKU offers greater control and flexibility for customization. Your choice affects pricing, operational overhead, and feature availability, so the skill guides you to evaluate your team's operational maturity and workload requirements when selecting between them.
How should I configure AKS networking and security?
Azure Kubernetes covers AKS networking configuration including pod IP models (Azure CNI Overlay vs VNet-routable), subnet planning, and private API server setup for enhanced security. Security configuration includes Entra ID for identity and access control, pod security policies, network policies, and secrets management best practices. The skill emphasizes that networking choices are Day-0 decisions and recommends aligning security posture with your compliance requirements before cluster creation.
What AKS Day-0 checklist should I follow?
Azure Kubernetes provides a Day-0 checklist covering critical pre-provisioning decisions: SKU selection, networking model, API server access type, identity provider setup, and security policies. These decisions cannot be reversed post-creation. The skill also guides post-creation setup including observability with Container Insights, upgrade strategies, node pool configuration, and cost optimization tactics like Spot nodes and vertical pod autoscaling to ensure your cluster is production-ready.
How can I optimize AKS cost and performance?
Azure Kubernetes recommends multiple cost and performance optimization strategies: enable Spot nodes for non-critical workloads, use cluster autoscaler and pod autoscaling (HPA and VPA), rightsize pods based on actual resource usage, and monitor costs through Container Insights. The skill guides you to balance performance requirements with cost constraints by selecting appropriate node types, configuring auto-scaling policies, and regularly reviewing resource utilization to eliminate waste.
How do I set up AKS observability and upgrade governance?
Azure Kubernetes guides AKS observability setup using Container Insights and Managed Prometheus for monitoring cluster health and workload performance. For operational governance, the skill covers upgrade strategies to keep your cluster current and secure, node pool management for staged rollouts, and validation procedures to confirm cluster readiness. These practices ensure visibility into cluster operations and controlled, predictable updates across your infrastructure.
SKILL.md
rendered from the published skill — quoted content, verbatim
Azure Kubernetes Service
> AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE > > This skill produces a recommended AKS cluster configuration based on user requirements, distinguishing Day-0 decisions (networking, API server — hard to change later) from Day-1 features (can enable post-creation). See CLI reference for commands.
Quick Reference
| Property | Value |
|---|---|
| Best for | AKS cluster |
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 11 files
skills/azure-kubernetes/SKILL.md
skills/azure-kubernetes/azure-kubernetes-automatic-readiness/SKILL.md
skills/azure-kubernetes/azure-kubernetes-automatic-readiness/references/common-fixes.md
skills/azure-kubernetes/azure-kubernetes-automatic-readiness/references/constraint-spec-v1.yaml
skills/azure-kubernetes/azure-kubernetes-automatic-readiness/references/mcp-integration.md
skills/azure-kubernetes/azure-kubernetes-automatic-readiness/references/migration-guide-summary.md
skills/azure-kubernetes/references/azure-aks-autoscaler.md
skills/azure-kubernetes/references/azure-aks-rightsizing.md
skills/azure-kubernetes/references/azure-aks-spot.md
skills/azure-kubernetes/references/azure-aks-vpa.md
skills/azure-kubernetes/references/cli-reference.md