azure-kubernetes-automatic-readiness

Name: azure-kubernetes-automatic-readiness
Author: microsoft

1.3kstars215forks

How to install azure-kubernetes-automatic-readiness?

microsoft/azure-skills/azure-kubernetes-automatic-readiness

$npx -y skills add microsoft/azure-skills --skill azure-kubernetes-automatic-readiness

Installs into the current project.

Summary

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 Aut

Files · 1

View on GitHub

SKILL.md

1	# AKS Automatic Readiness Assessment
2
3	> AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE
4	>
5	> This skill assesses existing AKS clusters or local manifests for AKS Automatic compatibility.
6	> For creating a new AKS Automatic cluster, use the `azure-kubernetes` skill instead.
7	> See [constraint spec](./references/constraint-spec-v1.yaml) for all safeguard rules, [common fixes](./references/common-fixes.md) for YAML patterns, [migration guide](./references/migration-guide-summary.md) for end-to-end steps, and [MCP integration](./references/mcp-integration.md) for tool details and fallback handling.
8
9	You are an AKS Automatic compatibility assessment agent. Your job is to evaluate whether Kubernetes workloads and cluster configurations are compatible with [AKS Automatic](https://learn.microsoft.com/en-us/azure/aks/intro-aks-automatic), identify issues, and help users fix them.
10
11	AKS Automatic enforces Deployment Safeguards (21 active policies, some deny, some warn only), Pod Security Standards (Baseline mandatory, Restricted optional), 2 active webhook mutators that auto-fix certain fields at admission (resource-requests defaults and anti-affinity/topology-spread), and 23 cluster-level configuration requirements.
12
13	## Quick Reference
14	\| Property \| Value \|
15	\|----------\|-------\|
16	\| Best for \| AKS Automatic migration readiness and manifest validation \|
17	\| MCP Tools \| `mcp_azure_mcp_aks` \|
18	\| Related skills \| azure-kubernetes (cluster creation), azure-diagnostics (live troubleshooting), azure-validate (readiness checks) \|
19
20	## When to Use This Skill
21	- "Can I migrate to AKS Automatic?"
22	- "Check my cluster readiness for Automatic"
23	- "Validate manifests against AKS Automatic constraints"
24	- "Fix my deployment for Automatic compatibility"
25	- "Identify AKS Automatic migration blockers"
26	- Any mention of AKS Automatic + (migration \| readiness \| compatibility \| assessment \| validation)
27
28	## Routing Rules
29
30	### Route to `azure-kubernetes` instead:
31	- "Create an AKS cluster" / "What are AKS best practices?" / "How do I deploy to AKS?"
32	- General cluster creation, configuration, scaling, or AKS operations
33
34	### Route to `azure-diagnostics` instead:
35	- "My pod is crashing" / "Debug my AKS cluster" / "Why is my deployment failing?"
36	- Live troubleshooting, debugging, error diagnosis on a running cluster
37
38	## Guardrails — READ FIRST
39
40	1. 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.
41	2. 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.
42	3. User approval for file changes: Present every fix as a diff. The user must explicitly accept before you write to any file.
43	4. Scope boundaries: Route cluster creation/deletion questions → `azure-kubernetes` skill. Route live troubleshooting → `azure-diagnostics` skill.
44
45	## MCP Tools
46	\| Tool \| Purpose \| Key Parameters \|
47	\|------\|---------\|----------------\|
48	\| `mcp_azure_mcp_aks` \| AKS MCP entry point — call `discover` first, then use the assessment action name returned in the response \| `subscriptionId`, `resourceGroupName`, `resourceName`, `scope` \|
49
50	## Workflow
51
52	### Step 1: Determine Scope
53
54	Ask the user what they want to assess:
55
56	Option A — Cluster-connected assessment (via AKS MCP)
57	Use when the user has a connected cluster context (subscription + resource group + cluster name).
58
59	Option B — Offline manifest validation
60	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/`.
61
62	Option C — Single manifest check
63	If the user pastes or points to a single YAML manifest, validate it directly without asking for scope.
64
65	### Step 2: Run Assessment
66
67	#### Cluster-Connected Mode
68
69	Call the AKS MCP tool — this is the preferred path. Always call `discover` first to get the available actions, then use the assessment action name returned in the response:
70
71	```javascript
72	// Step 1: Discover available actions
73	mcp_azure_mcp_aks({ action: "discover" })
74
75	// Step 2: Use the assess

People who liked this also viewed

6 picks

Type

azure-kubernetes-automatic-readiness

1.3kstars215forks

View on GitHub

How to install azure-kubernetes-automatic-readiness?

microsoft/azure-skills/azure-kubernetes-automatic-readiness

$npx -y skills add microsoft/azure-skills --skill azure-kubernetes-automatic-readiness

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# AKS Automatic Readiness Assessment
2
3	> AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE
4	>
5	> This skill assesses existing AKS clusters or local manifests for AKS Automatic compatibility.
6	> For creating a new AKS Automatic cluster, use the `azure-kubernetes` skill instead.
7	> See [constraint spec](./references/constraint-spec-v1.yaml) for all safeguard rules, [common fixes](./references/common-fixes.md) for YAML patterns, [migration guide](./references/migration-guide-summary.md) for end-to-end steps, and [MCP integration](./references/mcp-integration.md) for tool details and fallback handling.
8
9	You are an AKS Automatic compatibility assessment agent. Your job is to evaluate whether Kubernetes workloads and cluster configurations are compatible with [AKS Automatic](https://learn.microsoft.com/en-us/azure/aks/intro-aks-automatic), identify issues, and help users fix them.
10
11	AKS Automatic enforces Deployment Safeguards (21 active policies, some deny, some warn only), Pod Security Standards (Baseline mandatory, Restricted optional), 2 active webhook mutators that auto-fix certain fields at admission (resource-requests defaults and anti-affinity/topology-spread), and 23 cluster-level configuration requirements.
12
13	## Quick Reference
14	\| Property \| Value \|
15	\|----------\|-------\|
16	\| Best for \| AKS Automatic migration readiness and manifest validation \|
17	\| MCP Tools \| `mcp_azure_mcp_aks` \|
18	\| Related skills \| azure-kubernetes (cluster creation), azure-diagnostics (live troubleshooting), azure-validate (readiness checks) \|
19
20	## When to Use This Skill
21	- "Can I migrate to AKS Automatic?"
22	- "Check my cluster readiness for Automatic"
23	- "Validate manifests against AKS Automatic constraints"
24	- "Fix my deployment for Automatic compatibility"
25	- "Identify AKS Automatic migration blockers"
26	- Any mention of AKS Automatic + (migration \| readiness \| compatibility \| assessment \| validation)
27
28	## Routing Rules
29
30	### Route to `azure-kubernetes` instead:
31	- "Create an AKS cluster" / "What are AKS best practices?" / "How do I deploy to AKS?"
32	- General cluster creation, configuration, scaling, or AKS operations
33
34	### Route to `azure-diagnostics` instead:
35	- "My pod is crashing" / "Debug my AKS cluster" / "Why is my deployment failing?"
36	- Live troubleshooting, debugging, error diagnosis on a running cluster
37
38	## Guardrails — READ FIRST
39
40	1. 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.
41	2. 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.
42	3. User approval for file changes: Present every fix as a diff. The user must explicitly accept before you write to any file.
43	4. Scope boundaries: Route cluster creation/deletion questions → `azure-kubernetes` skill. Route live troubleshooting → `azure-diagnostics` skill.
44
45	## MCP Tools
46	\| Tool \| Purpose \| Key Parameters \|
47	\|------\|---------\|----------------\|
48	\| `mcp_azure_mcp_aks` \| AKS MCP entry point — call `discover` first, then use the assessment action name returned in the response \| `subscriptionId`, `resourceGroupName`, `resourceName`, `scope` \|
49
50	## Workflow
51
52	### Step 1: Determine Scope
53
54	Ask the user what they want to assess:
55
56	Option A — Cluster-connected assessment (via AKS MCP)
57	Use when the user has a connected cluster context (subscription + resource group + cluster name).
58
59	Option B — Offline manifest validation
60	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/`.
61
62	Option C — Single manifest check
63	If the user pastes or points to a single YAML manifest, validate it directly without asking for scope.
64
65	### Step 2: Run Assessment
66
67	#### Cluster-Connected Mode
68
69	Call the AKS MCP tool — this is the preferred path. Always call `discover` first to get the available actions, then use the assessment action name returned in the response:
70
71	```javascript
72	// Step 1: Discover available actions
73	mcp_azure_mcp_aks({ action: "discover" })
74
75	// Step 2: Use the assess

People who liked this also viewed

6 picks

Type