AKS Known Issues

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites: No account, no API key and no paid service is needed to install the skill or to look a signature up in its local catalog. To verify a fix against a live cluster you need your own Azure and AKS access (an Azure account with an AKS cluster, billed by Microsoft under your own agreement, plus read only Azure tools or CLI queries), and you must supply the exact error signature text from your own incident. At use time the skill can run read only Azure or CLI queries against your own subscription if you ask for verification; otherwise it works from the signature you paste and the local catalog. Nothing is sent anywhere during installation, and the skill requires your explicit approval before any mutation. Install "AKS Known Issues" for me. A narrow lookup, not a general troubleshooter. The skill applies only when your prompt includes an exact catalog signature with all of its qualifiers (for example VMCannotFitEphemeralOSDisk, NodePoolMcVersionIncompatible, a ZonalAllocationFailed with insufficient zone capacity, or a nested VMExtensionError with its outbound, API server or DNS qualifier). It looks the signature up in its error code map, and returns the cause, the fix, a Microsoft Learn citation and a read only verification. If any qualifier is missing, or the problem is a quota error, a bare wrapper or a generic symptom, the skill must not be used: generic AKS work belongs to aks-troubleshooting. It ships SKILL.md plus the catalog file references/error-code-map.md. Repository: https://github.com/microsoft/azure-skills (the skill is the whole .github/plugins/aks-skills/skills/aks-known-issues/ folder at the pinned commit: SKILL.md, references/error-code-map.md) Pinned version: install the code at commit cf79ce8778ad063eeac19dbe8bf982d71b466ce0 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/microsoft/azure-skills into a temporary folder, check out commit cf79ce8778ad063eeac19dbe8bf982d71b466ce0, and copy the .github/plugins/aks-skills/skills/aks-known-issues/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-18: [FINGERPRINTS] - SKILL.md: SHA-256 cb8520de767456a29e99e4321903e501946b3b8de06c0cc79fa0f2b938521791 - references/error-code-map.md: SHA-256 a1da03825b25e38256f6924748c5e661543a024f1e2141ddaa96cffc62e8830d If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full (and every other file in the folder) and tell me in plain words: what the skill does when used, which services it connects to, whether it reads or sends any personal information or keys, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 2 files: SKILL.md and references/error-code-map.md (the catalog). There is no executable code and no MCP tool is required. - Nothing is sent anywhere during installation itself; the only download is the skill folder from GitHub at the pinned commit. - At use time the lookup is local to the catalog. Optional verification uses read only Azure tools or CLI queries against your own subscription, only when you ask for it. - SKILL.md is strict about scope: every qualifier of a catalog row must be present, codes are not substrings, quota errors have no catalog rows, and explicit approval is required before every mutation. 3. When I say "yes, install", install it as a skill: copy the whole folder into the agent's skills directory, in a folder named "aks-known-issues", keeping every file (SKILL.md, references/error-code-map.md). 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (for example: sign in or create an account, provide any API key, or install any local tool named in the prerequisites; using the skill is a separate step that only starts when I ask for it, and every paid or authenticated use disclosed above happens only then). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.