Open aabond opened 2 years ago
Hello @aabond,
thanks for the request. I guess there will be adaptions on the configuration for multiple components are required. First of course the obvious things to do:
For the cloud-controller-manager we will need to update the cloud-provider-config by adding the cloud="USGovernmentCloud"
. Same for the csi/kube-controller-manager cloud-provider-configs.
See here: https://kubernetes-sigs.github.io/cloud-provider-azure/install/configs
We need also to adapt the mcm provider for Azure so that the correct environment is chosen: https://github.com/gardener/machine-controller-manager-provider-azure/blob/master/pkg/spi/azure.go#L36
And last we need also adapt the internal Azure client setup of the Azure extension.
/assign
/unassign as currently there is no active work on this
How to categorize this issue?
/area control-plane /area usability /area robustness /kind enhancement /priority 1 /platform azure
What would you like to be added:
Need the ability to deploy shoot clusters on Azure US Government Cloud. It seems the Azure infrastructure secret needs the ability to distinguish between Azure commercial and Azure US Government clouds. This parameter should then be provided to the underlying terraform code to switch to the Azure US Government API endpoint.
Why is this needed:
SAP NS2 needs to deploy SAP FieldGlass on to Azure US Government Cloud.
Current error being displayed while trying to deploy shoot cluster to Azure US Government:
Further notes: I came across this post when searching for the error:
https://serverfault.com/questions/1064253/azure-runbook-fails-to-connect-confidential-client-is-not-supported-in-cross
Which basically said adding the flag -Environment AzureUSGovernment solved their issue.