Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

{AKS} Implicitly enable istio when ingress gateway is enabled for Azure Service Mesh #7240

Closed
wants to merge 13 commits into from

Conversation

deveshdama
Copy link
Contributor


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

Related command

az aks mesh enable-ingress-gateway

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.

Copy link

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

Copy link

azure-client-tools-bot-prd bot commented Feb 1, 2024

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

Copy link

Hi @deveshdama,
Since the current milestone time is less than 7 days, this pr will be reviewed in the next milestone.

@yonzhan
Copy link
Collaborator

yonzhan commented Feb 1, 2024

AKS

@@ -13,6 +13,7 @@ Pending
+++++++
* Deprecate the alias "-r" of parameter --source-resource-id in `az aks trustedaccess rolebinding create`
* Refactor azure service mesh related code to meet cli style requirements.
* Implicitly enable istio when ingress or egress gateway is enabled for Azure Service Mesh.
Copy link
Member

Choose a reason for hiding this comment

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

Could you rebase/merge latest main? History note have changed here.

Ealianis and others added 9 commits February 4, 2024 16:02
* Add support for reconcile commands and update version to 1.0.3

* WIP - Enable hubprofile PUT for Fleet.

* Logic Checks

* Revert "Logic Checks"

This reverts commit 63f35a7.

* Revert "WIP - Enable hubprofile PUT for Fleet."

This reverts commit 8fdd475.

* Updated history.

* Added it_match & lint fix.

* Updated test.

* test update

* Update test results

* lint fix, help text added.

* typo fix

* Removed testing code.

Co-authored-by: Jim Minter <[email protected]>

---------

Co-authored-by: Jim Minter <[email protected]>
…gned and --mi-user-assigned, support 'az containerapp env identity assign/remove/show' (#7226)
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.

None yet