chore: fix e2e test using eastus2 region by default (#181)

examples/getting-started/README.md

@@ -53,7 +53,7 @@ the Azure resources needed**. To use the script, run
 ```sh
 # You can use other resource group names and locations as you see fit.
 export RESOURCE_GROUP=fleet-networking-tutorial
-export LOCATION=eastus
+export LOCATION=eastus2
 # Replace YOUR-CONTAINER-REGISTRY with a name of your own; do NOT use the full URL, i.e. specify
 # `bravelion` rather than `bravelion.azurecr.io`.
 export REGISTRY=YOUR-CONTAINER-REGISTRY
@@ -73,12 +73,12 @@ subscription manually:
 
 ### Create a resource group
 
-Run the commands below to create a resource group named `fleet-networking-tutorial` in the `eastus` location;
+Run the commands below to create a resource group named `fleet-networking-tutorial` in the `eastus2` location;
 you can use a different name or location as you see fit.
 
 ```sh
 export RESOURCE_GROUP=fleet-networking-tutorial
-export LOCATION=eastus
+export LOCATION=eastus2
 az group create --name $RESOURCE_GROUP --location $LOCATION
 ```
 
@@ -258,7 +258,7 @@ will use these IDs to authenticate themselves with the hub cluster.
     - Open [Azure portal][portal], and type `resource groups` in the search box at the top of the page. 
     - Click `Resource groups` in the list of matching services.
     - Find the resource group named `MC_[YOUR-RESOURCE-GROUP]_[YOUR-MEMBER-CLUSTER-1]_[YOUR-LOCATION]`, e.g.
-        `MC_fleet-networking-tutorial_member-1_eastus`, in the list, and click on the name.
+        `MC_fleet-networking-tutorial_member-1_eastus2`, in the list, and click on the name.
     - Find a managed identity resource named `[YOUR-MEMBER-CLUSTER-1]-agentpool`, e.g. `member-1-agentpool`, in
         the list of resources shown at the popped panel, and click on the name.
     - The client ID and principal ID is listed on the new page. Write down the two values:

test/scripts/bootstrap.sh

@@ -12,7 +12,7 @@ az account set -s ${AZURE_SUBSCRIPTION_ID}
 # Create resource group to host hub and member clusters.
 # RANDOM ID promises workflow runs don't interface one another.
 export RESOURCE_GROUP="${AZURE_RESOURCE_GROUP:-fleet-networking-e2e-$RANDOM}"
-export LOCATION="${LOCATION:-eastus}"
+export LOCATION="${LOCATION:-eastus2}"
 az group create --name $RESOURCE_GROUP --location $LOCATION --tags "source=fleet-networking"
 
 # Defer function to recycle created Azure resource.
@@ -67,14 +67,14 @@ case $AZURE_NETWORK_SETTING in
                 bash test/scripts/aks-dynamic-ip-allocation.sh
                 ;;
         peered-vnet)
-                export MEMBER_1_LOCATION="${MEMBER_1_LOCATION:-eastus}"
+                export MEMBER_1_LOCATION="${MEMBER_1_LOCATION:-eastus2}"
                 export MEMBER_2_LOCATION="${MEMBER_2_LOCATION:-westus}"
                 bash test/scripts/aks-peered-vnet.sh
                 ;;
         perf-test)
                 export MEMBER_CLUSTER_3=member-3
                 export MEMBER_CLUSTER_4=member-4
-                export MEMBER_LOCATION_1="${MEMBER_LOCATION_1:-eastus}"
+                export MEMBER_LOCATION_1="${MEMBER_LOCATION_1:-eastus2}"
                 export MEMBER_1_LOCATION=$MEMBER_LOCATION_1
                 export MEMBER_2_LOCATION=$MEMBER_LOCATION_1
                 export MEMBER_LOCATION_2="${MEMBER_LOCATION_2:=westus}"