Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[AVM Module Issue]: When deploying to NorthCentral AKS template fails precheck due to no availability zones in the region #4434

Open
1 task done
MikeHirtWB opened this issue Feb 11, 2025 · 4 comments
Assignees
Labels
Class: Resource Module 📦 This is a resource module Needs: Triage 🔍 Maintainers need to triage still Status: Response Overdue 🚩 When an issue/PR has not been responded to for X amount of days Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue Type: Bug 🐛 Something isn't working

Comments

@MikeHirtWB
Copy link

MikeHirtWB commented Feb 11, 2025

Check for previous/existing GitHub issues

  • I have checked for previous/existing GitHub issues

Issue Type?

Bug

Module Name

avm/res/container-service/managed-cluster

(Optional) Module Version

0.8.1

Description

When using the AVM for AKS and deploying to North Central US the prechecks fail for the module as Availability Zones are not allowed in this region.

I have tried setting the availability Zones property to null as well as setting 0 availability zones and this issue still shows up.

Example terminal output when doing a what-if deployment:


InvalidTemplateDeployment - The template deployment 'test-deploy' is not valid according to the validation procedure. The tracking id is 'e7b02c41-35d9-4c60-9c87-cb9fdb3778aa'. See inner errors for details.
AvailabilityZoneNotSupported - Preflight validation check for resource(s) for container service wbinfdaks01 in resource group cloudappsquad-dev-rg failed. Message: Availability zone is not supported in region northcentralus.. Details:

(Optional) Correlation Id

No response

@MikeHirtWB MikeHirtWB added Needs: Triage 🔍 Maintainers need to triage still Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue labels Feb 11, 2025

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

@microsoft-github-policy-service microsoft-github-policy-service bot added the Type: Bug 🐛 Something isn't working label Feb 11, 2025
@avm-team-linter avm-team-linter bot added the Class: Resource Module 📦 This is a resource module label Feb 11, 2025
Copy link

@MikeHirtWB, thanks for submitting this issue for the avm/res/container-service/managed-cluster module!

Important

A member of the @Azure/avm-res-containerservice-managedcluster-module-owners-bicep or @Azure/avm-res-containerservice-managedcluster-module-contributors-bicep team will review it soon!

Warning

Tagging the AVM Core Team (@Azure/avm-core-team-technical-bicep) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

Tip

  • To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
  • To avoid this rule being (re)triggered, the ""Needs: Triage 🔍" label must be removed as part of the triage process (when the issue is first responded to)!

@microsoft-github-policy-service microsoft-github-policy-service bot added the Status: Response Overdue 🚩 When an issue/PR has not been responded to for X amount of days label Feb 17, 2025
@MikeHirtWB
Copy link
Author

I was able to get the AVM's to work by just passing an empty array in for the Availability zones settings. Maybe I'm being knit picky here but that should probably be in the documentation for that parameter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Class: Resource Module 📦 This is a resource module Needs: Triage 🔍 Maintainers need to triage still Status: Response Overdue 🚩 When an issue/PR has not been responded to for X amount of days Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue Type: Bug 🐛 Something isn't working
Projects
Status: Needs: Triage
Development

No branches or pull requests

2 participants