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
Copy file name to clipboardExpand all lines: articles/openshift/create-private-cluster.md
+22-24Lines changed: 22 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,17 +80,15 @@ Next, you will create a virtual network containing two empty subnets.
80
80
```console
81
81
LOCATION=eastus #the location of your cluster
82
82
RESOURCEGROUP="v4-$LOCATION" #the name of the resource group where you want to create your cluster
83
-
CLUSTER=cluster #the name of your cluster
83
+
CLUSTER=aro-cluster #the name of your cluster
84
84
```
85
85
86
86
1.**Create a resource group**
87
87
88
88
An Azure resource group is a logical group in which Azure resources are deployed and managed. When you create a resource group, you are asked to specify a location. This location is where resource group metadata is stored, it is also where your resources run in Azure if you don't specify another region during resource creation. Create a resource group using the [az group create][az-group-create] command.
89
89
90
-
The following example creates a resource group named *aro-rg* in the *eastus* location.
91
-
92
90
```azurecli-interactive
93
-
az group create --name aro-rg --location eastus
91
+
az group create --name $RESOURCEGROUP --location $LOCATION
94
92
```
95
93
96
94
The following example output shows the resource group created successfully:
@@ -108,17 +106,17 @@ Next, you will create a virtual network containing two empty subnets.
108
106
}
109
107
```
110
108
111
-
3. **Create a virtual network.**
109
+
2. **Create a virtual network.**
112
110
113
111
Azure Red Hat OpenShift clusters running OpenShift 4 require a virtual network with two empty subnets, for the master and worker nodes.
114
112
115
-
Create a new virtual network in the same resource group you created earlier, for example in *aro-rg*.
113
+
Create a new virtual network in the same resource group you created earlier.
116
114
117
115
```azurecli-interactive
118
116
az network vnet create \
119
-
--resource-group aro-rg \
117
+
--resource-group $RESOURCEGROUP \
120
118
--name aro-vnet \
121
-
--address-prefixes 10.0.0.0/8
119
+
--address-prefixes 10.0.0.0/22
122
120
```
123
121
124
122
The following example output shows the virtual network created successfully:
@@ -128,7 +126,7 @@ Next, you will create a virtual network containing two empty subnets.
@@ -141,34 +139,34 @@ Next, you will create a virtual network containing two empty subnets.
141
139
}
142
140
```
143
141
144
-
4. **Add an empty subnet for the master nodes.**
142
+
3. **Add an empty subnet for the master nodes.**
145
143
146
144
```azurecli-interactive
147
145
az network vnet subnet create \
148
-
--resource-group aro-rg \
146
+
--resource-group $RESOURCEGROUP \
149
147
--vnet-name aro-vnet \
150
148
--name master-subnet \
151
-
--address-prefixes 10.0.1.0/24 \
149
+
--address-prefixes 10.0.0.0/23 \
152
150
--service-endpoints Microsoft.ContainerRegistry
153
151
```
154
152
155
-
5. **Add an empty subnet for the worker nodes.**
153
+
4. **Add an empty subnet for the worker nodes.**
156
154
157
155
```azurecli-interactive
158
156
az network vnet subnet create \
159
-
--resource-group aro-rg \
157
+
--resource-group $RESOURCEGROUP \
160
158
--vnet-name aro-vnet \
161
159
--name worker-subnet \
162
-
--address-prefixes 10.1.0.0/20 \
160
+
--address-prefixes 10.0.1.0/23 \
163
161
--service-endpoints Microsoft.ContainerRegistry
164
162
```
165
163
166
-
6. **[Disable subnet private endpoint policies](https://docs.microsoft.com/azure/private-link/disable-private-link-service-network-policy) on the master subnet.** This is required to be able to connect and manage the cluster.
164
+
5. **[Disable subnet private endpoint policies](https://docs.microsoft.com/azure/private-link/disable-private-link-service-network-policy) on the master subnet.** This is required to be able to connect and manage the cluster.
0 commit comments