Application Gateway for Containers addon commands

[JackStromberg]

---

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

Related command

• az aks applicationloadbalancer enable: Enable Application Load Balancer add-on for an existing cluster.
• az aks applicationloadbalancer disable: Disable Application Load Balancer add-on for an existing cluster.
• az aks applicationloadbalancer update: Update Application Load Balancer add-on for an existing cluster.

General Guidelines

• [yes] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• [yes] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• [yes] My extension version conforms to the Extension version schema

[azure-client-tools-bot-prd]

⚠️Azure CLI Extensions Breaking Change Test

⚠️aks-preview

rule	cmd_name	rule_message	suggest_message
⚠️ 1011 - SubgroupAdd	aks applicationloadbalancer	sub group aks applicationloadbalancer added
⚠️ 1006 - ParaAdd	aks create	cmd aks create added parameter enable_application_load_balancer

[azure-client-tools-bot-prd]

Hi @JackStromberg,
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.

[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>

[yonzhan]

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

[github-actions]

Hi @JackStromberg

Release Suggestions

Module: aks-preview

• Update VERSION to 19.0.0b17 in src/aks-preview/setup.py

Notes

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

[Copilot]

Pull Request Overview

This PR adds support for the Application Load Balancer (Application Gateway for Containers) addon to AKS clusters. The implementation follows the pattern established for other special addons like web app routing.

Key changes:

• Adds new CLI commands az aks applicationloadbalancer enable/disable/update for managing the addon
• Integrates the addon into existing addon management infrastructure (aks addon enable/disable)
• Stores configuration in the cluster's ingress profile rather than the standard addon profile

Reviewed Changes

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

Show a summary per file

File	Description
managed_cluster_decorator.py	Adds getter method for the parameter and methods to set up and update the application load balancer profile in the ingress profile
custom.py	Implements the enable/disable/update commands and integrates with existing addon list/show/enable/disable functionality
commands.py	Registers the new aks applicationloadbalancer command group with enable, disable, and update commands
addonconfiguration.py	Adds handling for the applicationloadbalancer addon in the update_addons function
_help.py	Adds documentation for the new commands and updates addon descriptions; fixes typo in app routing help
_consts.py	Defines constants for the new addon name and adds it to the ADDONS dictionary and descriptions
HISTORY.rst	Documents the new feature in the pending release notes

[FumingZhang]

Could you please add a new scenario test case (may refer to existing examples from test_aks_commands.py) for the change?

[FumingZhang]

Queued live test against staging-westus2.

[github-actions]

CodeGen Tools Feedback Collection

Thank you for using our CodeGen tool. We value your feedback, and we would like to know how we can improve our product. Please take a few minutes to fill our codegen survey

[FumingZhang]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[FumingZhang]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[FumingZhang]

CI failed with error

      raise HttpResponseError(response=response, model=error, error_format=ARMErrorFormat)

E azure.core.exceptions.HttpResponseError: (PreviewFeatureNotRegistered) Preview feature Microsoft.ContainerService/ApplicationLoadBalancerPreview not registered.
E Code: PreviewFeatureNotRegistered
E Message: Preview feature Microsoft.ContainerService/ApplicationLoadBalancerPreview not registered.

https://dev.azure.com/azclitools/public/public%20Team/_build/results?buildId=282646&view=logs&j=ff866e8d-4875-52ff-9fd3-f181f728432c&t=64f04c5b-80b8-53a1-8045-e38ac626841b&l=4547

Does the feature flag verification allow bypassing with a custom features header? If it does, you can include the relevant header in your test case and rerun the live test to create a new recording file.

[JackStromberg]

Does the feature flag verification allow bypassing with a custom features header?

@FumingZhang no, registration of the feature is required.

[FumingZhang]

Okay, in that case, you can remove the case from the default test matrix at src/aks-preview/azcli_aks_live_test/configs/ext_matrix_default.json and run it in live mode in a subscription where the feature is registered. This will allow you to generate a recording file that should pass the CI check.