aks-migration-harness

name	aks-migration-harness
description	Validate AKS migration output for Kubernetes manifests and Helm charts. Use for: test aks migration, validate migrated manifests, validate migrated helm chart, golden fixture regression for aks migration.
license	MIT
metadata	{"author":"GitHub Copilot","version":"0.1.0"}

AKS Migration Harness

Use this skill to verify that a migration is both syntactically valid and operationally closer to AKS best practices than the source.

When To Use

Activate this skill when the user wants to:

• test migrated manifests before cluster deployment
• validate a migrated Helm chart
• run a local AKS migration regression harness
• prove that source and target fixtures still pass after edits

Rules

1. Validate both source fixtures and target fixtures.
2. Treat the source as a golden input and the migrated AKS artifacts as the golden target.
3. Check intent-level invariants, not only raw YAML syntax.
4. Fail the run when a required AKS invariant is missing from the target.
5. Keep the harness local-first. Only add live cluster smoke checks after local render and policy gates pass.
6. If a live AKS target exists, prefer mcp_azure_mcp_aks for cluster metadata and keep mutating tests opt-in.

Workflow

1. Load the playbook in references/harness-playbook.md
2. Run the local harness script if the repository provides one
3. Record pass and fail evidence in a Markdown report
4. Use TEST_PROMPTS.md to regression test the skill behavior itself

References

• references/harness-playbook.md
• TEST_PROMPTS.md