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
Previously Azure VMs didn't have an identity attached at creation, which
meant they couldn't perform actions requiring authentication via the
Azure metadata server.
As some roachtests require access to an Azure storage container to pull
and push fixtures, a User Managed Identity will now be assigned to the
VMs at creation in order to simplify the credentials management.
One `rp-roachtest` UMI has been created in each subscription used to run
roachtests. These UMIs have been assigned a `roachtest` role that grants
blob management in Azure storage containers in the same subscription.
Since VMs are only attached a single identity, this is compatible with
`DefaultAzureCredential` without specifying any other credentials.
The subscription scope ensures that no test-production fixtures will be
created or updated during tests development (in the `Sponsorship` sub),
and that the nightly tests triggered from TeamCity (in the `e2e-infra`
sub) will always be isolated.
This requires the creation of one storage account per subscription
roachtests are triggered on, and will require the tests to implement
logic to determine the storage account to use based on the current
subscription ID, which can be accessed via the `AZURE_SUBSCRIPTION_ID`
environment variable.
Epic: none
Release note: None
0 commit comments