aks-migration-assess

name	aks-migration-assess
description	Assess a vanilla Kubernetes manifest set or Helm chart for migration to Azure Kubernetes Service. Use for: assess k8s for aks, assess helm chart for aks, migration readiness for aks, brownfield kubernetes to aks, aks target baseline, aks migration report.
license	MIT
metadata	{"author":"GitHub Copilot","version":"0.1.0"}

AKS Migration Assessment

Use this skill before rewriting any Kubernetes artifact for AKS.

When To Use

Activate this skill when the user wants to:

• assess a plain Kubernetes manifest set for AKS
• assess a Helm chart for AKS
• produce an AKS migration readiness report
• decide which source concerns stay workload-local versus cluster-level
• map vanilla ingress, identity, scaling, and security patterns to AKS defaults

Rules

1. Assess first. Do not start rewriting manifests or charts before the inventory and target baseline are documented.
2. Split decisions into two buckets:
   • Day-0 cluster decisions: networking mode, ingress strategy, identity model, observability landing zone, upgrade channel
   • Day-1 workload decisions: probes, HPA, PDB, topology spread, service shape, network policy
3. Prefer AKS defaults unless the source workload proves otherwise:
   • Azure CNI Overlay
   • Microsoft Entra Workload ID
   • application routing add-on for HTTP ingress
   • managed Azure observability stack
4. If a live AKS cluster is already in scope, inspect it with mcp_azure_mcp_aks before locking cluster assumptions.
5. Never mutate the source directory. All migration outputs go to a sibling -aks directory at the workspace root.

Workflow

1. Inventory source artifacts
   • list workloads, services, ingress resources, secrets usage, autoscaling, policies, and environment-specific values
2. Classify workload behavior
   • HTTP or TCP exposure
   • stateful or stateless
   • identity and secret access
   • scale profile and availability target
3. Create the AKS target baseline
   • cluster assumptions
   • workload baseline
   • required migration deltas
4. Decide artifact strategy
   • raw manifests -> target manifests
   • Helm chart -> AKS-aware chart values/templates
   • mixed source -> keep both outputs explicit
5. Write the report using the exact template in references/assessment-template.md
6. Hand off to aks-manifest-migrate

Output

Follow references/output-contract.md.

The assessment report must be saved as:

<source-name>-aks/migration-assessment-report.md

References

• references/assessment-template.md
• references/output-contract.md