Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Azure Local Cannot redeploy AKS

Open
#57 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, kubernetes

Research direction

No repository file or test is named. Start by reproducing the Azure Local 10.2411.3.2 upgrade, AKS deletion, and redeployment sequence, then inspect AKS gallery image states with Azure CLI and review the cited K8sVersionValidation guidance. Done means the stale image failures are cleared and a replacement AKS cluster deploys successfully with the same information.

Written by the indexing model from the issue text.

Description

IMPORTANT: Do not share any personal data in the bug report. This repository is a public forum and this report will also be public.

Bug description
Deploy Azure Local cluster on the previous build 2411.1 then deploy an AKS cluster. Upgrade the cluster to 2411.3 and delete the previous AKS cluster, then attempt to redeploy AKS with the same information. The deployment will fail and upon further investigation all AKS images are in a failure state leaving non-available for deployment.

Deployment is failing with citing the following error:
admission webhook "vhybridakscluster.kb.io" denied the request: {
"result": "Failed",
"validationChecks": [
{
"name": "K8sVersionValidation",
"message": "Kubernetes version 1.29.4 is not ready for use on Linux. Please go to https://aka.ms/aksarccheckk8sversions for details of how to check the readiness of Kubernetes versions.",
"recommendation": "Please check https://aka.ms/AKSArcValidationErrors/K8sVersionValidation for recommendations"
}
]
}

Using Azure CLI all AKS gallery images are in a failure state:

Image

Following the troubleshooting guide in the deployment error message and running the following command:
az rest --headers "Authorization=Bearer $token" "Content-Type=application/json;charset=utf-8" --uri $url --method DELETE

Does not appear to delete anything as all kubernetesVersions/default still exist in an error state with no change.

Repro steps
Steps to reproduce the behavior:

  1. Deploy Azure Local cluster on the previous build 2411.1
  2. Deploy an AKS cluster
  3. Upgrade the cluster to 2411.3
  4. Delete the previous AKS cluster
  5. Redeploy AKS cluster with same information
  6. Deployment errors out stating that any Kubernetes version you have selected is "not ready for use on "

Expected behavior
AKS images should not all be in an error state and the AKS cluster should successfully deploy.

Environment (please complete the following information):

  • Build 10.2411.3.2
  • Two node switchless
  • Non-production
  • Region EastUS
Dominant language
PowerShell
Stars
78
Forks
60
Avg merge
5h 24m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/AzureLocal-Supportability

All issues in Azure/AzureLocal-Supportability

Similar issues

More CLI issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.