Skip to content

Conversation

@Winbobob
Copy link
Member


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

Related command

az aks create: --enable-gateway-api flag
az aks update: --enable-gateway-api flag

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:

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.

…- managed Gateway API ingress provider enablement no longer required
Copilot AI review requested due to automatic review settings January 12, 2026 19:55
@Winbobob Winbobob requested a review from FumingZhang as a code owner January 12, 2026 19:55
@azure-client-tools-bot-prd
Copy link

azure-client-tools-bot-prd bot commented Jan 12, 2026

️✔️Azure CLI Extensions Breaking Change Test
️✔️Non Breaking Changes

@azure-client-tools-bot-prd
Copy link

Hi @Winbobob,
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
Copy link
Collaborator

yonzhan commented Jan 12, 2026

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

@github-actions
Copy link

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>

@github-actions
Copy link

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

@github-actions
Copy link

github-actions bot commented Jan 12, 2026

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR removes the prerequisite that Gateway API requires an enabled managed Gateway API ingress provider (such as Azure Service Mesh). The changes update documentation, tests, and release notes to reflect that --enable-gateway-api can now be used independently.

Changes:

  • Updated help text to remove the prerequisite requirement from parameter descriptions and examples
  • Renamed and updated test to better reflect its scope (create AND update operations)
  • Removed test that validated the old prerequisite enforcement
  • Added TODO for future test covering standalone Gateway API usage
  • Updated HISTORY.rst with proper formatting and new entry describing the change

Reviewed changes

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

File Description
src/aks-preview/azext_aks_preview/tests/latest/test_aks_commands.py Renamed test function for clarity, removed test validating old prerequisite behavior, added TODO for future standalone Gateway API test
src/aks-preview/azext_aks_preview/_help.py Removed prerequisite mention from --enable-gateway-api parameter descriptions for both create and update commands, simplified example to not require Azure Service Mesh
src/aks-preview/HISTORY.rst Fixed bullet point indentation for Application Load Balancer entry, added new entry documenting the prerequisite removal

Copy link
Contributor

@jaiveerk jaiveerk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm with question about release documentation

@FumingZhang
Copy link
Member

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 2 pipeline(s).

random_name_length=17, name_prefix="clitest", location="centraluseuap"
)
def test_aks_create_with_gateway_api_and_azureservicemesh(
def test_aks_create_and_update_with_gateway_api_and_azureservicemesh(
Copy link
Member

@FumingZhang FumingZhang Jan 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Queued live test to validate the change, test passed!

Copy link
Member

@FumingZhang FumingZhang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@zhoxing-ms zhoxing-ms merged commit 4972a30 into Azure:main Jan 15, 2026
24 checks passed
@azclibot
Copy link
Collaborator

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

@Winbobob Winbobob deleted the zheweihu/f/remove-gateway-api-cli-managed-impl-enablement-check branch January 15, 2026 06:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AKS Auto-Assign Auto assign by bot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants