-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Adding more context to maintenance configuration description for Microsoft.ContainerService-2025-10-02-preview #38720
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
Merged
FumingZhang
merged 1 commit into
Azure:FumingZhang-containerservice-Microsoft.ContainerService-2025-10-02-preview
from
anushkasingh16:anushkasingh/fix-mtc-definition
Nov 14, 2025
Merged
Conversation
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
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.Comment generated by summarize-checks workflow run. |
f75a0b8 to
a4003c2
Compare
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
|
yewmsft
approved these changes
Nov 12, 2025
...ource-manager/Microsoft.ContainerService/aks/preview/2025-10-02-preview/managedClusters.json
Show resolved
Hide resolved
FumingZhang
reviewed
Nov 12, 2025
| "required": true, | ||
| "type": "string", | ||
| "description": "The name of the maintenance configuration." | ||
| "description": "The name of the maintenance configuration. Supported values are 'default', 'aksManagedAutoUpgradeSchedule', or 'aksManagedNodeOSUpgradeSchedule'." |
Member
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Please fix failed Swagger PrettierCheck
- Please make changes only to specification/containerservice/resource-manager/Microsoft.ContainerService/aks/preview/2025-10-02-preview/managedClusters.json in this PR. You can update the stable API (and it should be 2025-10-01, instead of 2025-09-01) in the dev-containerservice-Microsoft.ContainerService-2025-10-01 branch.
2ab1abe to
a4003c2
Compare
6c2435f
into
Azure:FumingZhang-containerservice-Microsoft.ContainerService-2025-10-02-preview
84 of 94 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
brownfield
Brownfield services will soon be required to convert to TypeSpec. See https://aka.ms/azsdk/typespec.
Container Service
resource-manager
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.
SDK configuration pull request
Purpose of this PR
Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:
tspconfig.yamltemplates:Getting help
Purpose of this PRandDue diligence checklist.write accessper aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Mergecomment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.queuedstate, please add a comment with contents/azp run.This should result in a new comment denoting a
PR validation pipelinehas started and the checks should be updated after few minutes.