[docs] Document AKS destroy cleanup ordering fix - #1620
Draft
aspire-repo-bot[bot] wants to merge 1 commit into
Draft
[docs] Document AKS destroy cleanup ordering fix#1620aspire-repo-bot[bot] wants to merge 1 commit into
aspire-repo-bot[bot] wants to merge 1 commit into
Conversation
Documents the new destroy-specific AKS credential acquisition from microsoft/aspire#19243, which lets 'aspire destroy' tear down AKS deployments without relying on the caller's ambient kubectl context. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
aspire-repo-bot
Bot
added
the
docs-from-code
14 tasks
Contributor
Author
Frontend HTML artifact readyThe latest frontend build uploaded the This comment updates automatically when a new frontend build artifact is uploaded. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents changes from microsoft/aspire#19243
@sebastienrosTargeting
release/13.6based on the source PR milestone13.6.Why
The source PR fixes
aspire destroyfor AKS deployments so it no longer depends on the caller's ambientkubectlcontext: it now acquires AKS credentials for the target cluster itself before running Helm cleanup, and orders Helm release removal, opted-in external charts, and cert-manager teardown before the Azure resource group is deleted. The PR body includes a "User-facing usage" section and a--apphost/--environmentCLI example, but the AKS docs page had no "Clean up resources" / destroy section at all — only a deploy-time reference to destroy-time uninstall behavior for external charts.What changed
Added a new Clean up resources section to
deployment/kubernetes/aks.mdx(after "Publish AKS artifacts", before "Azure-specific considerations") that:aspire destroycommand.KUBECONFIG=$(mktemp) aspire destroy --apphost ... --environment ... --non-interactive --yesexample for CI/CD usage.aspire destroyCLI command reference page.Files modified
src/frontend/src/content/docs/deployment/kubernetes/aks.mdx