Skip to content

Conversation

@bragi92
Copy link
Member

@bragi92 bragi92 commented Jan 15, 2021

Description

This PR is updating the AKS region to Log Analytics region mapping for the Container Insights service.
Both AKS and Log analytics have added new regions since the last update and this PR makes sure that we don't default to eastus for those new regions and actually map it to its proper location.

This is the final list that has been agreed upon by talking with the AKS, LA, Networking and other teams that use the default workspace naming convention.

Testing Guide

Scenario for testing:
Create an AKS cluster in one of the new regions with monitoring enabled (e.g. make sure the resource group is in a new region like: Norway East)
command ->
az aks create --resource-group myResourceGroup --name myAKSCluster --node-count 1 --enable-addons monitoring

Once this command finishes you should see that monitoring is enabled for this cluster and its sending data to the default norwayeast log analytics workspace.

You can check this by doing an 'az aks show --resource-group myResourceGroup --name myAKSCluster' and checking under the omsagent addon for the log analytics workspace id.

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.


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

@bragi92 bragi92 marked this pull request as ready for review January 15, 2021 21:27
@bragi92
Copy link
Member Author

bragi92 commented Jan 15, 2021

@fengzhou-msft This PR is now ready for review. I've confirmed with the associated teams and the region map, short codes being used are final.

@bragi92
Copy link
Member Author

bragi92 commented Jan 19, 2021

@fengzhou-msft Have a look at this PR when you get a chance. Its ready to merge

@bragi92
Copy link
Member Author

bragi92 commented Jan 25, 2021

@fengzhou-msft Have a look at this PR when you get a chance. Its ready to merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants