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

[Issue] host: aks fails on postprovision hook if iac doesn't include aks #3272

Open
jongio opened this issue Feb 1, 2024 · 2 comments
Open
Assignees
Labels
aks Azure Kubernetes Service extensibility
Milestone

Comments

@jongio
Copy link
Member

jongio commented Feb 1, 2024

I have a two phase provision:

phase 1

  1. provision openai
  2. run the app locally

phase 2:

  1. provision the rest of the services, including aks

when host is aks, azd will do an auto-post-provision hook to do aks deployments or config.

Since phase 1 doesn't have aks provisioned, then this will fail with:

ERROR: deployment failed: failed invoking event handlers for 'postprovision', failed retrieving cluster admin credentials. Ensure your cluster has been configured to support admin credentials, parameter resourceName cannot be empty

I would like the post-provision hook to fail gracefully if the aks resources don't exist.

@rajeshkamal5050
Copy link
Contributor

@wbreza can you take a look? Is this related some of the asks we had around provisioning with specific bicep files/resources or a service-level provisioning?

@wbreza
Copy link
Contributor

wbreza commented Mar 25, 2024

This partially aligns with some of the proposed for the new AI/ML apps support in azd.

Move target resource discovery to service targets

  • Right now target resource discovery occurs globally within azd. Some service targets support delayed provisioning and we currently have a less than ideal implementation.
  • Moving to target resource discovery to each service target will give additional flexibility for resource discovery and offer an improve implementation.
  • After this work is done we can also introduce standardized warnings/errors where a missing resource can be bubbled up correctly to the UX noting the deployment is skipped due to missing resource but continue with remaining services without throwing a fatal error.

@rajeshkamal5050 rajeshkamal5050 modified the milestones: Backlog, On Deck Mar 25, 2024
@rajeshkamal5050 rajeshkamal5050 modified the milestones: On Deck, Backlog Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aks Azure Kubernetes Service extensibility
Projects
None yet
Development

No branches or pull requests

3 participants