Content-Length: 352710 | pFad | http://github.com/Azure/azure-rest-api-specs/pull/34812

BC Add support for TargetKubernetesVesion channel by minhng22 · Pull Request #34812 · Azure/azure-rest-api-specs · GitHub
Skip to content

Add support for TargetKubernetesVesion channel #34812

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

Conversation

minhng22
Copy link
Contributor

@minhng22 minhng22 commented May 20, 2025

ARM (Control Plane) API Specification Update Pull Request

Tip

Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

spec_pr_review_workflow_diagram

Purpose of this PR

What's the purpose of this PR? Check the specific option that applies. This is mandatory!

  • New resource provider.
  • New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
  • Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
  • Update existing version to fix OpenAPI spec quality issues in S360.
  • Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
  • Other, please clarify:
    • edit this with your clarification

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:

  • I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
  • I have reviewed following Resource Provider guidelines, including
    ARM resource provider contract and
    REST guidelines (estimated time: 4 hours).
    I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
  • A release plan has been created. If not, please create one as it will help guide you through the REST API and SDK creation process.

Additional information

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

  • First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
  • If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
  • To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
  • For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
    and https://aka.ms/ci-fix.
  • For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
  • If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
    This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
  • If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Copy link

openapi-pipeline-app bot commented May 20, 2025

Next Steps to Merge

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

Copy link

openapi-pipeline-app bot commented May 20, 2025

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

@minhng22
Copy link
Contributor Author

LintDiff unrelated to changes in this PR

@frantran frantran merged commit 54e1f5a into Azure:dev-aks-fleet-2025-07-01-preview May 21, 2025
19 of 35 checks passed
frantran pushed a commit that referenced this pull request May 21, 2025
* Add support for TargetKubernetesVesion channel
---------

Co-authored-by: nguyenmin <nguyenmin@microsoft.com>
frantran added a commit that referenced this pull request May 30, 2025
* Copy files from stable/2025-03-01

Copied the files in a separate commit.
This allows reviewers to easily diff subsequent changes against the previous spec.

* Update version to preview/2025-07-01-preview

Updated the API version from stable/2025-03-01 to preview/2025-07-01-preview.

* add new version to readme and main

* Add support for TargetKubernetesVesion channel (#34812)

* Add support for TargetKubernetesVesion channel
---------

Co-authored-by: nguyenmin <nguyenmin@microsoft.com>

* try fix compile

* copy examples

* Delete AutoUpgradeProfiles_CreateOrUpdate copy.json

* Update fleets.json

---------

Co-authored-by: frantran <ftran@microsoft.com>
Co-authored-by: Minh Nguyen <comrc019@icloud.com>
Co-authored-by: nguyenmin <nguyenmin@microsoft.com>
@frantran frantran mentioned this pull request May 30, 2025
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants








ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: http://github.com/Azure/azure-rest-api-specs/pull/34812

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy