azure-kubernetes-automatic-readiness
Assesses cluster and manifest compatibility with AKS Automatic, providing fixes for deployment safeguards and security policies.
Install
mkdir -p .claude/skills/azure-kubernetes-automatic-readiness && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15352" && unzip -o skill.zip -d .claude/skills/azure-kubernetes-automatic-readiness && rm skill.zipInstalls to .claude/skills/azure-kubernetes-automatic-readiness
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Assess Kubernetes workloads and cluster configuration for AKS Automatic compatibility. Identifies incompatibilities, generates fixes, and guides migration from AKS Standard to AKS Automatic. WHEN: migrate to AKS Automatic, check AKS Automatic readiness, validate manifests for Automatic, assess cluster for Automatic compatibility, fix deployment for Automatic compatibility, identify AKS Automatic migration blockers, is my cluster ready for AKS Automatic.Key capabilities
- →Assess Kubernetes workloads for AKS Automatic compatibility
- →Identify incompatibilities with AKS Automatic
- →Generate fixes for deployment issues
- →Guide migration from AKS Standard to AKS Automatic
- →Validate manifests against AKS Automatic constraints
- →Assess cluster-level configuration requirements
How it works
This skill assesses AKS clusters or local manifests against AKS Automatic compatibility requirements, identifying policy violations and generating remediation steps.
Inputs & outputs
When to use azure-kubernetes-automatic-readiness
- →Migrating to AKS Automatic
- →Checking AKS cluster readiness
- →Validating kubernetes manifests
About this skill
AKS Automatic Readiness Assessment
AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE
This skill assesses existing AKS clusters or local manifests for AKS Automatic compatibility. For creating a new AKS Automatic cluster, use the
azure-kubernetesskill instead. See constraint spec for all safeguard rules, common fixes for YAML patterns, migration guide for end-to-end steps, and MCP integration for tool details and fallback handling.
You are an AKS Automatic compatibility assessment agent. Your job is to evaluate whether Kubernetes workloads and cluster configurations are compatible with AKS Automatic, identify issues, and help users fix them.
AKS Automatic enables Deployment Safeguards in Enforce mode by default (some rules deny, some warn only, some mutate), Pod Security Standards at Baseline (Restricted is opt-in), 2 active webhook mutators that auto-fix certain fields at admission (resource-requests defaults and anti-affinity/topology-spread), and a set of cluster-level configuration requirements. The bundled constraint spec is the rule source; rule counts in prose are descriptive, not proof of what a given cluster enforces.
Quick Reference
| Property | Value |
|---|---|
| Best for | AKS Automatic migration readiness and manifest validation |
| MCP Tools | Host-discovered Azure MCP AKS capability (mcp_azure_mcp_aks in GitHub Copilot) for cluster/node-pool reads; kubectl + jq for sanitized workload reads |
| Related skills | azure-kubernetes (cluster creation), azure-diagnostics (live troubleshooting), aks-troubleshooting (AKS-focused diagnosis when the aks-skills plugin is installed), azure-validate (readiness checks) |
When to Use This Skill
- "Can I migrate to AKS Automatic?"
- "Check my cluster readiness for Automatic"
- "Validate manifests against AKS Automatic constraints"
- "Fix my deployment for Automatic compatibility"
- "Identify AKS Automatic migration blockers"
- Any mention of AKS Automatic + (migration | readiness | compatibility | assessment | validation)
Routing Rules
Route to azure-kubernetes instead:
- "Create an AKS cluster" / "What are AKS best practices?" / "How do I deploy to AKS?"
- General cluster creation, configuration, scaling, or AKS operations
Route to azure-diagnostics instead:
- "My pod is crashing" / "Debug my AKS cluster" / "Why is my deployment failing?"
- Live troubleshooting, debugging, error diagnosis on a running cluster
Guardrails — READ FIRST
- Read-only: NEVER modify cluster state. Assessment is read-only. Do not run
kubectl apply,az aks update, or any command that changes the cluster. - No secrets: Do NOT transmit, display, or include in diffs: Secret data values, ConfigMap data values, environment variable values from
valueFrom.secretKeyRef, service account tokens, or connection strings. - User approval for file changes: Present every fix as a diff. The user must explicitly accept before you write to any file.
- Scope boundaries: Route cluster creation/deletion questions →
azure-kubernetesskill. Route live troubleshooting →azure-diagnosticsskill.
MCP Tools
| Capability | Purpose | Typical Parameters |
|---|---|---|
Azure MCP AKS capability discovered from the host's available tools (mcp_azure_mcp_aks in GitHub Copilot) | Read cluster and node-pool configuration. The documented surface is cluster get/list and node-pool get/list; it has no readiness-assessment operation | Use only the parameters in the host-advertised schema |
Host Kubernetes capability or kubectl piped through scripts/sanitize-readiness-input.jq | Read allowlisted workload fields for local evaluation against the bundled constraint spec | Cluster context, resource kinds, namespaces |
Workflow
Step 1: Determine Scope
Ask the user what they want to assess:
Option A — Cluster-connected assessment Use when the user has a connected cluster context (subscription + resource group + cluster name).
Option B — Offline manifest validation
Use when the user has local Kubernetes manifests, Helm charts, or Kustomize overlays in their workspace. Search for files containing apiVersion: and kind: matching Deployment, StatefulSet, DaemonSet, Job, CronJob, Pod, Service, PodDisruptionBudget, or StorageClass. For Helm charts, look for Chart.yaml and rendered templates under templates/.
Option C — Single manifest check If the user pastes or points to a single YAML manifest, validate it directly without asking for scope.
Step 2: Run Assessment
Cluster-Connected Mode
- Discover the host's approved AKS metadata capabilities; use their host-assigned names and schemas. Azure MCP, governed ARM tools, or a governed Azure CLI capability may provide the relevant reads. A missing literal name is not proof of absence.
- If using Azure MCP, use its advertised cluster/node-pool reads for metadata (SKU, network plugin, addons, node pool OS). The documented surface has no readiness-assessment operation — do not expect one (Azure MCP AKS tools).
- Read workloads through an approved host Kubernetes capability with allowlist projection, or, where the host permits shell/cluster access and exposes the bundled filter, pipe
kubectlJSON throughscripts/sanitize-readiness-input.jq(requiresjq) before anything reaches the model. Never fetchSecret/ConfigMap resources or paste rawkubectl -o json. If neither path is available, use offline or user-provided manifests; do not route Kubernetes commands through Azure MCP. - Evaluate metadata and manifests locally against
references/constraint-spec-v1.yaml. - Run
kubectl get constraintswhen reachable before reporting anyconditionalSafeguardsrule.
# from the skill root
set -o pipefail
kubectl get deployment,statefulset,daemonset,job,cronjob,pod,service,poddisruptionbudget,storageclass \
-A -o json |
jq -f scripts/sanitize-readiness-input.jq
Fallback Chain
Cluster metadata:
1. Host-discovered Azure MCP AKS cluster/node-pool read capability
↓ no matching capability, operation absent, or access fails
2. Host-approved equivalent metadata reads, including governed ARM/Azure CLI
capabilities or permitted `az aks show` and `az aks nodepool list`
Workload data:
1. Approved host Kubernetes read with projection, or permitted sanitized `kubectl | jq`
↓ execution/cluster access unavailable, or jq/bundled filter missing
2. Offline validation of local, rendered, or user-provided manifests
If no Azure MCP AKS tool is discovered, use the host's approved equivalent
metadata capabilities and continue with permitted sanitized Kubernetes reads
or offline validation. A local or external MCP server is not a prerequisite.
Suggest connector setup only where the host supports and authorizes it;
host-specific options are in references/mcp-integration.md. Do not bypass
the host's governed tool boundary to obtain missing evidence.
Offline Mode
Load references/constraint-spec-v1.yaml and evaluate every manifest against every rule: check says what and which fields to inspect, fix gives allowed values and remediations. Suggest needed fixes.
Key checks: Per container (containers, initContainers, ephemeralContainers):
- Resource requests/limits →
safeguard-container-resource-requests - Readiness and liveness probes →
safeguard-probes-configured(warning-only — not blocked at admission; treat as informational) - Image tag not
:latest→safeguard-images-no-latest securityContext.privilegednot true →safeguard-no-privileged-containerscapabilities.addonly adds allowed capabilities →safeguard-container-capabilitiesseccompProfileis RuntimeDefault/Localhost →safeguard-allowed-seccomp-profiles- no
hostfield in probes and lifecycle hooks →safeguard-host-probes(advisory/unverified — not a documented Automatic block)
Per pod spec:
hostPID/hostIPCnot true →safeguard-block-host-namespaces(incompatible)hostNetwork/hostPortnot true →safeguard-host-network-ports(incompatible)- No
hostPathvolumes →safeguard-no-host-path-volumes(incompatible)
Conditional (conditionalSafeguards — report only when applicable, never as default blockers):
allowPrivilegeEscalation, run-as-non-root, allowed volume types → PSS Restricted opt-in only (Learn marks these "PSS Restricted Only")- Windows
ContainerAdministrator→ Windows node pools only, when the constraint is active
Per workload type:
- Deployments/StatefulSets with replicas > 1: podAntiAffinity or topologySpreadConstraints →
safeguard-pod-enforce-antiaffinity - StorageClass: CSI provisioner (not in-tree) →
safeguard-csi-driver-storage-class
Severity Classification
| Severity | Meaning | Action |
|---|---|---|
incompatible | Fundamental architecture issue; cannot run on Automatic without redesign | Must fix before migration — flag prominently |
requiresChanges | Manifest changes needed; will be denied at admission | Generate fix diffs |
autoFixed | AKS Automatic will mutate this at admission; no user action needed | Informational — show what will change |
informational | Warning-only, advisory, or not enforced on the default Automatic Baseline | Mention briefly; never list as a blocker |
conditional (enforcement: conditional) | Enforced only under PSS Restricted, on Windows nodes, or when the cluster's active constraints include it | Report with its appliesWhen condition; confirm with kubectl get constraints when possible |
Step 3: Present Findings
Always start with the summary:
Content truncated.
When not to use it
- →When creating a new AKS Automatic cluster
- →When troubleshooting a live, running AKS cluster
- →When the task involves general AKS cluster creation, configuration, or scaling
Limitations
- →The skill is read-only and does not modify cluster state
- →The skill does not transmit or display secret data values
- →The skill bundles constraint spec v1.1.1 (2026-03-15)
How it compares
This skill specifically evaluates compatibility with AKS Automatic's enforced safeguards and configurations, providing targeted fixes, unlike general Kubernetes validation.
Compared to similar skills
azure-kubernetes-automatic-readiness side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| azure-kubernetes-automatic-readiness (this skill) | 0 | 5mo | No flags | Intermediate |
| linkerd-patterns | 6 | 8mo | Review | Advanced |
| managing-network-policies | 1 | 4mo | Review | Intermediate |
| azure-stack-edge | 0 | 7mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jonathan-vella
View all by jonathan-vella →You might also like
linkerd-patterns
wshobson
Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
managing-network-policies
jeremylongshore
Execute use when managing Kubernetes network policies and firewall rules. Trigger with phrases like "create network policy", "configure firewall rules", "restrict pod communication", or "setup ingress/egress rules". Generates Kubernetes NetworkPolicy manifests following least privilege and zero-trust principles.
azure-stack-edge
orgdevendra
Expert knowledge for Azure Stack Edge development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when running IoT Edge or GPU/Kubernetes apps, configuring VMs/storage/networking, or managing de
k8s-security
rohitg00
Audit Kubernetes RBAC, enforce policies, and manage secrets. Use for security reviews, permission audits, policy enforcement with Kyverno/Gatekeeper, and secret management.
container-security-testing
Ed1s0nZ
容器安全测试的专业技能和方法论
k8s-certs
rohitg00
Kubernetes certificate management with cert-manager. Use when managing TLS certificates, configuring issuers, or troubleshooting certificate issues.