Add special clouds to ev2 rollout - #1772
Merged
Merged
Conversation
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
suyadav1
commented
Aug 25, 2026
suyadav1
commented
Aug 25, 2026
Contributor
Author
|
/azp run |
|
Azure Pipelines: Successfully started running 1 pipeline(s). 2 pipeline(s) were filtered out due to trigger conditions. |
rashmichandrashekar (rashmichandrashekar)
approved these changes
Aug 26, 2026
Contributor
Author
|
/azp run |
suyadav1
enabled auto-merge (squash)
August 26, 2026 14:54
|
Azure Pipelines: Successfully started running 1 pipeline(s). 2 pipeline(s) were filtered out due to trigger conditions. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request updates the Azure Pipeline configuration for AKS extension managed Ev2 SDP rollouts. The main goals are to enable and standardize extension rollouts across all supported Azure clouds, update Helm chart URLs, and provide the necessary configuration overrides and rollout stages for each environment.
The most important changes are:
Pipeline and Stage Enablement:
FF_Managed_SDP) and Mooncake (MC_Managed_SDP) clouds, and adds new rollout stages for US National (USNat_Managed_SDP) and US Sec (USSec_Managed_SDP) clouds, ensuring managed SDP rollouts are performed for all supported clouds.Configuration Overrides per Cloud:
FairfaxConfigurationOverridesandMooncakeConfigurationOverridesvariables with the correctextensionTypeName,packageConfig,helmChartUrl, and cloud-specific managed identity values.USNatConfigurationOverrides) and US Sec (USSecConfigurationOverrides) clouds, including their respective Helm chart URLs and managed identities.Helm Chart URL Standardization:
helmChartUrlvalues in configuration overrides to use the new standardized path (mcr.microsoft.com/azuremonitor/helmchart/containerinsights/ciprod/azuremonitor-containersfor public, Fairfax, and Mooncake clouds, and cloud-specific URLs for USNat and USSec).Pipeline Cleanup:
.pipelines/azure-pipeline-aks-extension-managed-ev2-sdp-canary.ymlpipeline file, which is no longer needed due to the new central artifacts model.These changes ensure the pipeline can deploy the extension to all Azure clouds with the correct configuration and identity setup, using a consistent rollout process.