{AKS} add support to create cluster with kube-proxy configuration

[mattstam]

---

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

Related command

az aks create --kube-proxy-config file.json

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?

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.
The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify src/index.json.

[yonzhan]

AKS

[FumingZhang]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[FumingZhang]

Please fix the lint issues scanned by CI.

Also need to rebase from main (including this change) to fix failures in Integration Tests, Build Tests....

[mattstam]

Please the lint issues scanned by CI.

Also need to rebase from main (including this change) to fix failures in Integration Tests, Build Tests....

Rebased with main.

Locally I see some lint issue but they are not related to any of my changes from what I can tell, I think main just has lint issues in it?

[FumingZhang]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[FumingZhang]

Please the lint issues scanned by CI.
Also need to rebase from main (including this change) to fix failures in Integration Tests, Build Tests....

Rebased with main.

Locally I see some lint issue but they are not related to any of my changes from what I can tell, I think main just has lint issues in it?

Yeah, if the CI could pass, that would be fine.

[mattstam]

Azure.azure-cli-extensions (CLI Linter on Modified Extensions)

azure-cli-extensions (CLI Linter on Modified Extensions) would be the relevant CI here, right? That seems to pass. If there is any other changes needed, please let me know.

[FumingZhang]

Hey @mattstam, there are some errors in Azure.azure-cli-extensions (Static Analysis) need to be fixed.

/mnt/vss/_work/1/s/src/aks-preview/azext_aks_preview/managed_cluster_decorator.py:92:1: E302 expected 2 blank lines, found 1
/mnt/vss/_work/1/s/src/aks-preview/azext_aks_preview/managed_cluster_decorator.py:397:1: W293 blank line contains whitespace
/mnt/vss/_work/1/s/src/aks-preview/azext_aks_preview/managed_cluster_decorator.py:2392:45: E221 multiple spaces before operator

Besides, there's another NRP API version update in official CLI, which leads to the errors in Integration Tests, Build Tests..., fixing this in PR #5434. Please rebase from main later.

[mattstam]

Hey @mattstam, there are some errors in Azure.azure-cli-extensions (Static Analysis) need to be fixed.

/mnt/vss/_work/1/s/src/aks-preview/azext_aks_preview/managed_cluster_decorator.py:92:1: E302 expected 2 blank lines, found 1
/mnt/vss/_work/1/s/src/aks-preview/azext_aks_preview/managed_cluster_decorator.py:397:1: W293 blank line contains whitespace
/mnt/vss/_work/1/s/src/aks-preview/azext_aks_preview/managed_cluster_decorator.py:2392:45: E221 multiple spaces before operator

Besides, there's another NRP API version update in official CLI, which leads to the errors in Integration Tests, Build Tests..., fixing this in PR #5434. Please rebase from main later.

Thanks @FumingZhang, I have rebased with main and fixed all the lint issues in the AKS extension (including existing ones not related to the changes in this PR).

[FumingZhang]

LGTM

[azclibot]

[Release] Update index.json for extension [ aks-preview ] : https://dev.azure.com/azclitools/internal/_build/results?buildId=8169&view=results