New version of k8s-extension CLI (v1.8.0) using API version 2025-03-01

[prasannajsns]

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (azdev required; see .azure-pipelines/templates/azdev_setup.yml for the install command until azdev==0.2.11b1 is on PyPI)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[prasannajsns]

@yanzhudd I have fixed the CI failures related to added style. I tried triggering the '/azp run' but don't seem to have enough permissions. Are there any other steps to perform from our side? If not, can you please approve this PR?

[prasannajsns]

/azp run

[azure-pipelines]

Commenter does not have sufficient privileges for PR 10045 in repo Azure/azure-cli-extensions

[yanzhudd]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 2 pipeline(s).

[prasannajsns]

@yanzhudd - The /azp run reports failures on linter and style. However, I resolved all the styling errors already (Other individual checks for azdev style and linter checks passed). Could you please suggest if this can be ignored or anything needs to be fixed?

[prasannajsns]

@yonzhan @yanzhudd - some of our customers are waiting on this new CLI package. Could you please help take a look at my question on the CI job failures and help with merging this PR?

[yanzhudd]

Hi @prasannajsns could you please sync with the lastest code from the main branch?

[yanzhudd]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 2 pipeline(s).

[JaysonTaiMicrosoft]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 2 pipeline(s).

[JaysonTaiMicrosoft]

Hi @prasannajsns, could you sync with the latest code in main again. Another change to the index.json was made before azp was run causing the failure.

[NoriZC]

Hi @prasannajsns please sync main to fix the CI failure.

REF:
git checkout upstream/main -- src/index.json
git commit -m "Sync index.json with upstream main"
git push

[prasannajsns]

Hi @prasannajsns, could you sync with the latest code in main again. Another change to the index.json was made before azp was run causing the failure.

Hi @JaysonTaiMicrosoft - I have just merged the latest main from upstream to my branch. Could you please help trigger '/azp run' on this PR?

[JaysonTaiMicrosoft]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 2 pipeline(s).

[azclibot]

[Release] Update index.json for extension [ k8s-extension-1.8.0 ] : https://dev.azure.com/msazure/One/_build/results?buildId=172684225&view=results