{AKS} populate location of managed namespaces using managed cluster's location

[xmzhao0822]

---

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

Related command

az aks namespace add
az aks namespace update

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? (pip install wheel==0.30.0 required)
• 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.

[azure-client-tools-bot-prd]

️✔️Azure CLI Extensions Breaking Change Test

️✔️Non Breaking Changes

[azure-client-tools-bot-prd]

Hi @xmzhao0822,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[github-actions]

The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR.

Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

[Copilot]

Pull Request Overview

This PR populates managed namespace resources with the location of their parent AKS cluster by fetching and assigning the cluster’s location in both add and update commands.

• Fetch the AKS cluster location in aks_managed_namespace_add and aks_managed_namespace_update.
• Assign the cluster’s location to the location field on namespace_config.
• Adjust tests to mock get_mgmt_service_client and simulate cluster location.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
src/aks-preview/azext_aks_preview/tests/latest/test_managednamespace.py	Added get_mgmt_service_client patch and mock cluster client in tests to simulate location.
src/aks-preview/azext_aks_preview/managednamespace.py	Imported client factory & cluster client, fetched the cluster’s location, and set namespace_config.location in both add/update commands.

Comments suppressed due to low confidence (1)

src/aks-preview/azext_aks_preview/managednamespace.py:43

• The new location property assignment isn't covered by any tests. Add tests to verify that namespace_config.location is correctly set based on the cluster's location.

namespace_config.location = cluster_location

[github-actions]

• For more info about extension versioning, please refer to Extension version schema

[FumingZhang]

lgtm

Queued live test to validate the change.

• test_aks_managed_namespace

[FumingZhang]

lgtm

Queued live test to validate the change.

• test_aks_managed_namespace

live test failed with the following error

E azure.core.exceptions.ResourceExistsError: (CannotDeleteResource) Cannot delete resource while nested resources exist. Some existing nested resource IDs include: 'Microsoft.ContainerService/managedClusters/cliakstestvx3ffn/managedNamespaces/namespace01'. Please delete all nested resources before deleting this resource.
E Code: CannotDeleteResource
E Message: Cannot delete resource while nested resources exist. Some existing nested resource IDs include: 'Microsoft.ContainerService/managedClusters/cliakstestvx3ffn/managedNamespaces/namespace01'. Please delete all nested resources before deleting this resource.

[FumingZhang]

due to change in Azure/azure-cli#31589, the CI checks failed, could you please replace 2024-07-01 with 2022-09-01 in file src/aks-preview/azext_aks_preview/tests/latest/recordings/test_aks_create_and_update_outbound_ips.yaml

[FumingZhang]

live test passed

[azclibot]

[Release] Update index.json for extension [ aks-preview-18.0.0b8 ] : https://dev.azure.com/msazure/One/_build/results?buildId=126094133&view=results