mirror of
https://github.com/MicrosoftLearning/AZ-104-MicrosoftAzureAdministrator.git
synced 2026-02-04 23:59:08 +00:00
Merge pull request #582 from theadzik/master
Fix Portal UI and Lab instructions incompatibilities
This commit is contained in:
commit
6df80c7697
@ -200,7 +200,7 @@ In this task, you will create an Azure Active Directory user, assign the RBAC ro
|
||||
|
||||
1. Select **Refresh** to verify that the subscription has successfully moved to the **Tenant Root management group**.
|
||||
|
||||
1. Navigate back to the **Management groups** blade, right click the **ellipsis** icon to the right of the **az104-02-mg1** management group and click **Delete**.
|
||||
1. Navigate back to the **Management groups** blade, click the **ellipsis** icon to the right of the **az104-02-mg1** management group and click **Delete**.
|
||||
|
||||
#### Review
|
||||
|
||||
|
||||
@ -144,7 +144,7 @@ In this task, we will use a different policy definition to remediate any non-com
|
||||
|
||||
1. In the **Authoring** section, click **Assignments**.
|
||||
|
||||
1. In the list of assignments, right click the ellipsis icon in the row representing the **Require Role tag with Infra value** policy assignment and use the **Delete assignment** menu item to delete the assignment.
|
||||
1. In the list of assignments, click the ellipsis icon in the row representing the **Require Role tag with Infra value** policy assignment and use the **Delete assignment** menu item to delete the assignment.
|
||||
|
||||
1. Click **Assign policy** and specify the **Scope** by clicking the ellipsis button and selecting the following values:
|
||||
|
||||
|
||||
@ -322,7 +322,7 @@ In this task, you will configure and test routing between the two spoke virtual
|
||||
| --- | --- |
|
||||
| Route name | **az104-06-route-vnet2-to-vnet3** |
|
||||
| Address prefix destination | **IP Addresses** |
|
||||
| Source IP addresses/CIDR ranges | **10.63.0.0/20** |
|
||||
| Destination IP addresses/CIDR ranges | **10.63.0.0/20** |
|
||||
| Next hop type | **Virtual appliance** |
|
||||
| Next hop address | **10.60.0.4** |
|
||||
|
||||
@ -365,7 +365,7 @@ In this task, you will configure and test routing between the two spoke virtual
|
||||
| --- | --- |
|
||||
| Route name | **az104-06-route-vnet3-to-vnet2** |
|
||||
| Address prefix destination | **IP Addresses** |
|
||||
| Source IP addresses/CIDR ranges | **10.62.0.0/20** |
|
||||
| Destination IP addresses/CIDR ranges | **10.62.0.0/20** |
|
||||
| Next hop type | **Virtual appliance** |
|
||||
| Next hop address | **10.60.0.4** |
|
||||
|
||||
|
||||
@ -106,7 +106,7 @@ In this task, you will create and configure an Azure Storage account.
|
||||
|
||||
1. Click **Next: Advanced >**, on the **Advanced** tab of the **Create storage account** blade, review the available options, accept the defaults, and click **Next: Networking >**.
|
||||
|
||||
1. On the **Networking** tab of the **Create storage account** blade, review the available options, accept the default option **Public endpoint (all networks}** and click **Next: Data protection >**.
|
||||
1. On the **Networking** tab of the **Create storage account** blade, review the available options, accept the default option **Enable public access from all networks** and click **Next: Data protection >**.
|
||||
|
||||
1. On the **Data protection** tab of the **Create storage account** blade, review the available options, accept the defaults, click **Review + Create**, wait for the validation process to complete and click **Create**.
|
||||
|
||||
|
||||
@ -40,7 +40,7 @@ In this task, you will deploy Azure virtual machines into different availability
|
||||
|
||||
1. Sign in to the [Azure portal](http://portal.azure.com).
|
||||
|
||||
1. In the Azure portal, search for and select **Virtual machines** and, on the **Virtual machines** blade, click **+ Create**, click **+ Virtual machine**.
|
||||
1. In the Azure portal, search for and select **Virtual machines** and, on the **Virtual machines** blade, click **+ Create**, click **+ Azure virtual machine**.
|
||||
|
||||
1. On the **Basics** tab of the **Create a virtual machine** blade, specify the following settings (leave others with their default values):
|
||||
|
||||
|
||||
@ -173,11 +173,6 @@ In this task, you will scale horizontally the number of pods and then number of
|
||||
1. From the **Cloud Shell** pane, and run the following to scale the deployment by increasing of the number of pods to 2:
|
||||
|
||||
```sh
|
||||
|
||||
RESOURCE_GROUP='az104-09c-rg1'
|
||||
|
||||
AKS_CLUSTER='az104-9c-aks1'
|
||||
|
||||
kubectl scale --replicas=2 deployment/nginx-deployment
|
||||
```
|
||||
|
||||
@ -192,6 +187,10 @@ In this task, you will scale horizontally the number of pods and then number of
|
||||
1. From the **Cloud Shell** pane, run the following to scale out the cluster by increasing the number of nodes to 2:
|
||||
|
||||
```sh
|
||||
RESOURCE_GROUP='az104-09c-rg1'
|
||||
|
||||
AKS_CLUSTER='az104-9c-aks1'
|
||||
|
||||
az aks scale --resource-group $RESOURCE_GROUP --name $AKS_CLUSTER --node-count 2
|
||||
```
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user