AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

azure-kubernetes

Plan, create, and configure production-ready Azure Kubernetes Service (AKS) clusters. Covers Day-0 checklist, SKU selection (Automatic vs Standard), networking options (private API server, Azure CNI Overlay, egress configuration), security, and operations (autoscaling, upgrade strategy, cost analysis). WHEN: create AKS environment, provision AKS, enable AKS observability, design AKS networking, choose AKS SKU, secure AKS, optimize AKS, AKS spot nodes, AKS cluster-autoscaler, rightsize AKS pod, pod rightsizing, over-provisioned AKS pod, pod resource requests and limits, Vertical Pod Autoscaler, VPA recommendations.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-kubernetes at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 8

references/azure-aks-nap-readiness.md

Base NAP Readiness

Use this limited readiness check when aks-cost-optimization is unavailable or declined. The optional skill provides deeper workload-fit, alternatives, cost, and migration analysis.

Collect Cluster State and Choose the Workflow

Prefer a fitting Azure MCP AKS read. If unavailable and shell access is approved, collect only the required fields:

az aks show \
  --name "<CLUSTER_NAME>" --resource-group "<RESOURCE_GROUP>" \
  --query "{sku:sku.name,mode:nodeProvisioningProfile.mode,identity:identity.type,outboundType:networkProfile.outboundType,network:{plugin:networkProfile.networkPlugin,pluginMode:networkProfile.networkPluginMode,dataplane:networkProfile.networkDataplane,policy:networkProfile.networkPolicy,ipFamilies:networkProfile.ipFamilies,loadBalancerSku:networkProfile.loadBalancerSku},pools:agentPoolProfiles[].{name:name,os:osType,cas:enableAutoScaling,min:minCount,max:maxCount,count:count,subnet:vnetSubnetId,podSubnet:podSubnetId,podIpAllocationMode:podIpAllocationMode}}" \
  -o json
  • If mode is Auto, NAP is already enabled; do not rerun enablement readiness.
  • For a Standard cluster without NAP, present two assessment paths: use the checks below for existing-cluster NAP eligibility, or invoke azure-kubernetes-automatic-readiness when available for AKS Automatic migration compatibility. AKS Automatic is preferred for most production workloads.

Check Eligibility

Do not recommend NAP for Windows pools, IPv6, service-principal identity, Basic Load Balancer in a custom VNet, kubenet, Calico network policy, or Azure CNI Pod Subnet with dynamic individual IP allocation.

Confirm acceptance that NAP removes cluster stop/start support and constrains outbound-type changes.

If CAS is enabled, do not recommend NAP through this base workflow. Invoke aks-cost-optimization when available to compare CAS tuning with a controlled CAS-to-NAP migration. Otherwise, explain that migration requires either disabling CAS first or a temporary, explicitly approved side-by-side transition using the subscription-wide AllowClusterAutoscalerAndNAP feature and mutually exclusive scheduling. State that neither migration path was assessed here.

Decide

This base workflow assesses configuration eligibility only. If no blocker is found, configuration eligibility alone does not justify NAP enablement; report the cluster as potentially eligible and identify workload-fit and cost analysis as missing. Require explicit approval before NAP enablement.