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/aks/cluster-configuration.md
+15-2Lines changed: 15 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,6 +44,8 @@ When the status shows as registered, refresh the registration of the `Microsoft.
44
44
az provider register --namespace Microsoft.ContainerService
45
45
```
46
46
47
+
### New clusters
48
+
47
49
Configure the cluster to use Ubuntu 18.04 when the cluster is created. Use the `--aks-custom-headers` flag to set the Ubuntu 18.04 as the default OS.
48
50
49
51
```azure-cli
@@ -52,6 +54,17 @@ az aks create --name myAKSCluster --resource-group myResourceGroup --aks-custom-
52
54
53
55
If you want to create a regular Ubuntu 16.04 cluster, you can do so by omitting the custom `--aks-custom-headers` tag.
54
56
57
+
### Existing clusters
58
+
59
+
Configure a new node pool to use Ubuntu 18.04. Use the `--aks-custom-headers` flag to set the Ubuntu 18.04 as the default OS for that node pool.
60
+
61
+
```azure-cli
62
+
az aks nodepool add --name ubuntu1804 --cluster-name myAKSCluster --resource-group myResourceGroup --aks-custom-headers CustomizedUbuntu=aks-ubuntu-1804
63
+
```
64
+
65
+
If you want to create a regular Ubuntu 16.04 node pools, you can do so by omitting the custom `--aks-custom-headers` tag.
66
+
67
+
55
68
## Custom resource group name
56
69
57
70
When you deploy an Azure Kubernetes Service cluster in Azure, a second resource group gets created for the worker nodes. By default, AKS will name the node resource group `MC_resourcegroupname_clustername_location`, but you can also provide your own name.
@@ -62,9 +75,9 @@ To specify your own resource group name, install the aks-preview Azure CLI exten
62
75
az aks create --name myAKSCluster --resource-group myResourceGroup --node-resource-group myNodeResourceGroup
63
76
```
64
77
65
-
The secondary resource group is automatically created by the Azure resource provider in your own subscription. Note that you can only specify the custom resource group name when the cluster is created.
78
+
The secondary resource group is automatically created by the Azure resource provider in your own subscription. You can only specify the custom resource group name when the cluster is created.
66
79
67
-
As you work with the node resource group, keep in mind that you cannot:
80
+
As you work with the node resource group, keep in mind that you can't:
68
81
69
82
- Specify an existing resource group for the node resource group.
70
83
- Specify a different subscription for the node resource group.
Copy file name to clipboardExpand all lines: articles/aks/kubernetes-walkthrough-portal.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,7 @@ To create an AKS cluster, complete the following steps:
45
45
46
46
4. On the **Scale** page, keep the default options. At the bottom of the screen, click **Next: Authentication**.
47
47
> [!CAUTION]
48
-
> Creating new AAD Service Principals may take multiple minutes to propagate and become available causing Service Principal not found errors and validation failures in Azure portal. If you hit this please visit [here](troubleshooting.md#im-receiving-errors-that-my-service-principal-was-not-found-when-i-try-to-create-a-new-cluster-without-passing-in-an-existing-one) for mitigations.
48
+
> Creating new AAD Service Principals may take multiple minutes to propagate and become available causing Service Principal not found errors and validation failures in Azure portal. If you hit this please visit [here](troubleshooting.md#received-an-error-saying-my-service-principal-wasnt-found-or-is-invalid-when-i-try-to-create-a-new-cluster) for mitigation.
49
49
50
50
5. On the **Authentication** page, configure the following options:
51
51
- Create a new service principal by leaving the **Service Principal** field with **(new) default service principal**. Or you can choose *Configure service principal* to use an existing one. If you use an existing one, you will need to provide the SPN client ID and secret.
0 commit comments