Repository navigation
[docs] Document AKS Standard control-plane tier default - #1872
Draft
aspire-repo-bot[bot] wants to merge 1 commit into
Draft
aspire-repo-bot[bot] wants to merge 1 commit into
aspire-repo-bot[bot] wants to merge 1 commit into
Conversation
Adds a Cluster tier section to both the AKS hosting integration reference and the Deploy to AKS guide, describing the new Standard default, its uptime SLA and cluster-management charge, and how to opt back into the Free tier via ConfigureInfrastructure. Documents changes from microsoft/aspire#20917. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
4 of 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#20917.
@mitchdennyTarget branch
Targeting
release/17.0based on the source PR milestone17.0(exact match onmicrosoft/aspire.dev).Why this PR is needed
microsoft/aspire#20917 changes the default AKS control-plane tier for Aspire-managed clusters from Free to Standard, ahead of the integration moving toward general availability. This is a user-visible default-value change that affects billing (adds a cluster-management charge) and availability guarantees for every AppHost using
AddAzureKubernetesEnvironment, with no corresponding mention in the existingaspire.devdocs for the AKS integration.Triggered signals from the docs-check pre-step:
integration_readme_changed—src/Aspire.Hosting.Azure.Kubernetes/README.mdadded a "Cluster tier" section in the source PR.pr_body_has_user_facing_section— the source PR body's "User-facing usage" section shows the new generatedsku: { name: 'Base', tier: 'Standard' }and theConfigureInfrastructureoverride to keep Free.pr_body_has_cli_flag_mention— matched on validation command text in the PR body (not an actual CLI flag, but confirms the recall-oriented doc-gap check was warranted here since the behavior change itself had no doc coverage).What documentation was added
Added a new Cluster tier section (mirroring the source PR's README update) to:
src/frontend/src/content/docs/integrations/cloud/azure/aks/index.mdx— the AKS hosting integration API reference.src/frontend/src/content/docs/deployment/kubernetes/aks.mdx— the end-to-end "Deploy to AKS" guide.Both sections explain:
ConfigureInfrastructure, using the exact C# snippet from the source PR.Files modified
src/frontend/src/content/docs/integrations/cloud/azure/aks/index.mdx(updated — existing page)src/frontend/src/content/docs/deployment/kubernetes/aks.mdx(updated — existing page)No new pages were created; both are existing pages for the AKS integration area.
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
registry.npmjs.orgTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.