You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We cannot use azwi to create either a service account or a federated identity in the AzureUSGovernment cloud. The endpoint that is being hit to look up our subscription-id is the public endpoint, not the AzureUSGovernment endpoint and thus when our subscription-id is queried it returns a 404. When using --azure-env to set it to AzureUSGovernment or AzureUSGovernmentCloud, the setting is ignored.
NOTE: This also doesn't work with Windows 10 using azwi for powershell either.
Kernel (e.g. uname -a): Linux <HOSTNAME> 5.4.72-microsoft-standard-WSL2 #1 SMP Wed Oct 28 23:40:43 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Install tools: I installed this by grabbing the release from github: wget https://github.com/Azure/azure-workload-identity/releases/download/v1.2.1/azwi-v1.2.1-linux-amd64.tar.gz and then moving to /usr/bin/azwi
Additional context
When attempting to run the commands on the guide we can tell that it's reaching out to the wrong endpoint, hence the 404 when looking up our subscription-id. We are attempting to set this up in order to support the usage of external secrets operator by following their instructions to use azwi. I noticed there's a ticket open already about it not working in non-public clouds (#566 ) We are also not sure why Error: header "WWW-Authenticate" not found in get subscription response is being returned in the logs, but since it doesn't match the anticipated outcome in the guide, we presume it's due to the cloud API endpoint being incorrect.
The text was updated successfully, but these errors were encountered:
We cannot use azwi to create either a service account or a federated identity in the AzureUSGovernment cloud. The endpoint that is being hit to look up our subscription-id is the public endpoint, not the AzureUSGovernment endpoint and thus when our subscription-id is queried it returns a 404. When using
--azure-env
to set it to AzureUSGovernment or AzureUSGovernmentCloud, the setting is ignored.Steps To Reproduce
and
Expected behavior
Based on the documentation found here the following output or some version thereof should be generated, but it doesn't work.
INFO[0000] No subscription provided, using selected subscription from Azure CLI: REDACTED INFO[0032] [federated-identity] added federated credential objectID=REDACTED subject="system:serviceaccount:default:workload-identity-sa"
Logs
First is for attempting to create a service account:
The next is attempting to create a federated identity:
Environment
Azure USGoverment GCC High IL-4
kubectl version
):cat /etc/os-release
):NOTE: This also doesn't work with Windows 10 using azwi for powershell either.
uname -a
):Linux <HOSTNAME> 5.4.72-microsoft-standard-WSL2 #1 SMP Wed Oct 28 23:40:43 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
wget https://github.com/Azure/azure-workload-identity/releases/download/v1.2.1/azwi-v1.2.1-linux-amd64.tar.gz
and then moving to/usr/bin/azwi
Additional context
When attempting to run the commands on the guide we can tell that it's reaching out to the wrong endpoint, hence the 404 when looking up our subscription-id. We are attempting to set this up in order to support the usage of external secrets operator by following their instructions to use azwi. I noticed there's a ticket open already about it not working in non-public clouds (#566 ) We are also not sure why
Error: header "WWW-Authenticate" not found in get subscription response
is being returned in the logs, but since it doesn't match the anticipated outcome in the guide, we presume it's due to the cloud API endpoint being incorrect.The text was updated successfully, but these errors were encountered: