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/active-directory/fundamentals/whats-new.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -163,12 +163,12 @@ Update the company branding functionality on the Azure AD/Microsoft 365 sign in
163
163
164
164
165
165
**Type:** New feature
166
-
**Service category:**B2B
167
-
**Product capability:**B2B/B2C
166
+
**Service category:**Directory Management
167
+
**Product capability:**Directory
168
168
169
-
Administrative Units now support soft deletion. Admins can now list, view properties of, perform ad hoc hard delete, or restore deleted Administrative Units using Microsoft Graph. This functionality restores all configuration for the Administrative Unit when restored from soft delete including: memberships, admin roles, processing rules, and processing rules state.
169
+
Administrative Units now support soft deletion. Admins can now list, view properties of, or restore deleted Administrative Units using the Microsoft Graph. This functionality restores all configuration for the Administrative Unit when restored from soft delete, including memberships, admin roles, processing rules, and processing rules state.
170
170
171
-
This functionality greatly enhances recoverability and resilience when using Administrative Units. Now, when an Administrative Unit is accidentally deleted, it can be restored quickly to the same state it was at time of deletion. This removes uncertainty around how things were configured, and makes restoration quick and easy. For more information, see: [Soft deletions](../fundamentals/recover-from-deletions.md#soft-deletions).
171
+
This functionality greatly enhances recoverability and resilience when using Administrative Units. Now, when an Administrative Unit is accidentally deleted it can be restored quickly to the same state it was at time of deletion-removing uncertainty around how things were configured and making restoration quick and easy. For more information, see: [List deletedItems (directory objects)](/graph/api/directory-deleteditems-list?view=graph-rest-1.0&tabs=http).
# Tutorial: Deploy an Azure Kubernetes Service (AKS) cluster
14
14
15
-
Kubernetes provides a distributed platform for containerized applications. With AKS, you can quickly create a production ready Kubernetes cluster. In this tutorial, part three of seven, a Kubernetes cluster is deployed in AKS. You learn how to:
15
+
Kubernetes provides a distributed platform for containerized applications. With AKS, you can quickly create a production ready Kubernetes cluster. In this tutorial, part three of seven, you deploy a Kubernetes cluster in AKS. You learn how to:
16
16
17
17
> [!div class="checklist"]
18
-
> * Deploy a Kubernetes AKS cluster that can authenticate to an Azure container registry
19
-
> * Install the Kubernetes CLI (kubectl)
20
-
> * Configure kubectl to connect to your AKS cluster
21
18
22
-
In later tutorials, the Azure Vote application is deployed to the cluster, scaled, and updated.
19
+
> * Deploy a Kubernetes AKS cluster that can authenticate to an Azure Container Registry (ACR).
20
+
> * Install the Kubernetes CLI, `kubectl`.
21
+
> * Configure `kubectl` to connect to your AKS cluster.
23
22
24
-
## Before you begin
25
-
26
-
In previous tutorials, a container image was created and uploaded to an Azure Container Registry instance. If you haven't done these steps, and would like to follow along, start at [Tutorial 1 – Create container images][aks-tutorial-prepare-app].
23
+
In later tutorials, you'll deploy the Azure Vote application to your AKS cluster and scale and update your application.
27
24
28
-
### [Azure CLI](#tab/azure-cli)
29
-
30
-
This tutorial requires that you're running the Azure CLI version 2.0.53 or later. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI][azure-cli-install].
25
+
## Before you begin
31
26
32
-
### [Azure PowerShell](#tab/azure-powershell)
27
+
In previous tutorials, you created a container image and uploaded it to an ACR instance. If you haven't done these steps and would like to follow along, start with [Tutorial 1: Prepare an application for AKS][aks-tutorial-prepare-app].
33
28
34
-
This tutorial requires that you're running Azure PowerShell version 5.9.0 or later. Run `Get-InstalledModule -Name Az` to find the version. If you need to install or upgrade, see [Install Azure PowerShell][azure-powershell-install].
29
+
* If you're using Azure CLI, this tutorial requires that you're running the Azure CLI version 2.0.53 or later. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI][azure-cli-install].
30
+
* If you're using Azure PowerShell, this tutorial requires that you're running Azure PowerShell version 5.9.0 or later. Run `Get-InstalledModule -Name Az` to find the version. If you need to install or upgrade, see [Install Azure PowerShell][azure-powershell-install].
35
31
36
32
---
37
33
38
34
## Create a Kubernetes cluster
39
35
40
-
AKS clusters can use Kubernetes role-based access control (Kubernetes RBAC). These controls let you define access to resources based on roles assigned to users. Permissions are combined if a user is assigned multiple roles, and permissions can be scoped to either a single namespace or across the whole cluster. By default, the Azure CLI automatically enables Kubernetes RBAC when you create an AKS cluster.
36
+
AKS clusters can use [Kubernetes role-based access control (Kubernetes RBAC)][k8s-rbac], which allows you to define access to resources based on roles assigned to users. If a user is assigned multiple roles, permissions are combined. Permissions can be scoped to either a single namespace or across the whole cluster.
37
+
38
+
To learn more about AKS and Kubernetes RBAC, see [Control access to cluster resources using Kubernetes RBAC and Azure Active Directory identities in AKS][aks-k8s-rbac].
41
39
42
40
### [Azure CLI](#tab/azure-cli)
43
41
44
-
Create an AKS cluster using [az aks create][]. The following example creates a cluster named *myAKSCluster* in the resource group named *myResourceGroup*. This resource group was created in the [previous tutorial][aks-tutorial-prepare-acr] in the *eastus* region. The following example does not specify a region so the AKS cluster is also created in the *eastus* region. For more information, see [Quotas, virtual machine size restrictions, and region availability in Azure Kubernetes Service (AKS)][quotas-skus-regions] for more information about resource limits and region availability for AKS.
42
+
Create an AKS cluster using [`az aks create`][az aks create]. The following example creates a cluster named *myAKSCluster* in the resource group named *myResourceGroup*. This resource group was created in the [previous tutorial][aks-tutorial-prepare-acr] in the *eastus* region. The AKS cluster will also be created in the *eastus* region.
43
+
44
+
For more information about AKS resource limits and region availability, see [Quotas, virtual machine size restrictions, and region availability in AKS][quotas-skus-regions].
45
45
46
-
To allow an AKS cluster to interact with other Azure resources, a cluster identity is automatically created, since you did not specify one. Here, this cluster identity is [granted the right to pull images][container-registry-integration] from the Azure Container Registry (ACR) instance you created in the previous tutorial. To execute the command successfully, you're required to have an **Owner** or **Azure account administrator** role on the Azure subscription.
46
+
To allow an AKS cluster to interact with other Azure resources, a cluster identity is automatically created. In this example, the cluster identity is [granted the right to pull images][container-registry-integration] from the ACR instance you created in the previous tutorial. To execute the command successfully, you're required to have an **Owner** or **Azure account administrator** role in your Azure subscription.
47
47
48
48
```azurecli
49
49
az aks create \
@@ -56,9 +56,11 @@ az aks create \
56
56
57
57
### [Azure PowerShell](#tab/azure-powershell)
58
58
59
-
Create an AKS cluster using [New-AzAksCluster][new-azakscluster]. The following example creates a cluster named *myAKSCluster* in the resource group named *myResourceGroup*. This resource group was created in the [previous tutorial][aks-tutorial-prepare-acr] in the *eastus* region. The following example does not specify a region so the AKS cluster is also created in the *eastus* region. For more information, see [Quotas, virtual machine size restrictions, and region availability in Azure Kubernetes Service (AKS)][quotas-skus-regions] for more information about resource limits and region availability for AKS.
59
+
Create an AKS cluster using [`New-AzAksCluster`][new-azakscluster]. The following example creates a cluster named *myAKSCluster* in the resource group named *myResourceGroup*. This resource group was created in the [previous tutorial][aks-tutorial-prepare-acr] in the *eastus* region. The AKS cluster will also be created in the *eastus* region.
60
60
61
-
To allow an AKS cluster to interact with other Azure resources, a cluster identity is automatically created, since you did not specify one. Here, this cluster identity is [granted the right to pull images][container-registry-integration] from the Azure Container Registry (ACR) instance you created in the previous tutorial. To execute the command successfully, you're required to have an **Owner** or **Azure account administrator** role on the Azure subscription.
61
+
For more information about AKS resource limits and region availability, see [Quotas, virtual machine size restrictions, and region availability in AKS][quotas-skus-regions].
62
+
63
+
To allow an AKS cluster to interact with other Azure resources, a cluster identity is automatically created. In this example, the cluster identity is [granted the right to pull images][container-registry-integration] from the ACR instance you created in the previous tutorial. To execute the command successfully, you're required to have an **Owner** or **Azure account administrator** role in your Azure subscription.
To avoid needing an **Owner** or **Azure account administrator** role, you can also manually configure a service principal to pull images from ACR. For more information, see [ACR authentication with service principals](../container-registry/container-registry-auth-service-principal.md) or [Authenticate from Kubernetes with a pull secret](../container-registry/container-registry-auth-kubernetes.md). Alternatively, you can use a [managed identity](use-managed-identity.md) instead of a service principal for easier management.
70
72
71
-
After a few minutes, the deployment completes, and returns JSON-formatted information about the AKS deployment.
73
+
After a few minutes, the deployment completes and returns JSON-formatted information about the AKS deployment.
72
74
73
75
> [!NOTE]
74
-
> To ensure your cluster to operate reliably, you should run at least 2 (two) nodes.
76
+
> To ensure your cluster operates reliably, you should run at least two nodes.
75
77
76
78
## Install the Kubernetes CLI
77
79
78
-
To connect to the Kubernetes cluster from your local computer, you use [kubectl][kubectl], the Kubernetes command-line client.
80
+
Use the Kubernetes CLI, [`kubectl`][kubectl], to connect to the Kubernetes cluster from your local computer.
79
81
80
82
### [Azure CLI](#tab/azure-cli)
81
83
82
-
If you use the Azure Cloud Shell, `kubectl` is already installed. You can also install it locally using the [az aks install-cli][] command:
84
+
If you use the Azure Cloud Shell, `kubectl` is already installed. You can also install it locally using the [`az aks install-cli`][az aks install-cli] command.
83
85
84
86
```azurecli
85
87
az aks install-cli
86
88
```
89
+
87
90
### [Azure PowerShell](#tab/azure-powershell)
88
91
89
-
If you use the Azure Cloud Shell, `kubectl` is already installed. You can also install it locally using the [Install-AzAksKubectl][install-azakskubectl] cmdlet:
92
+
If you use the Azure Cloud Shell, `kubectl` is already installed. You can also install it locally using the [`Install-AzAksKubectl`][install-azakskubectl] cmdlet.
90
93
91
94
```azurepowershell
92
95
Install-AzAksKubectl
@@ -98,23 +101,23 @@ Install-AzAksKubectl
98
101
99
102
### [Azure CLI](#tab/azure-cli)
100
103
101
-
To configure `kubectl` to connect to your Kubernetes cluster, use the [az aks get-credentials][] command. The following example gets credentials for the AKS cluster named *myAKSCluster* in the *myResourceGroup*:
104
+
To configure `kubectl` to connect to your Kubernetes cluster, use the [`az aks get-credentials`][az aks get-credentials] command. The following example gets credentials for the AKS cluster named *myAKSCluster* in *myResourceGroup*.
102
105
103
106
```azurecli
104
107
az aks get-credentials --resource-group myResourceGroup --name myAKSCluster
105
108
```
106
109
107
110
### [Azure PowerShell](#tab/azure-powershell)
108
111
109
-
To configure `kubectl` to connect to your Kubernetes cluster, use the [Import-AzAksCredential][import-azakscredential] cmdlet. The following example gets credentials for the AKS cluster named *myAKSCluster* in the *myResourceGroup*:
112
+
To configure `kubectl` to connect to your Kubernetes cluster, use the [`Import-AzAksCredential`][import-azakscredential] cmdlet. The following example gets credentials for the AKS cluster named *myAKSCluster* in *myResourceGroup*.
Copy file name to clipboardExpand all lines: articles/aks/use-azure-dedicated-hosts.md
+21-11Lines changed: 21 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Use Azure Dedicated Hosts in Azure Kubernetes Service (AKS)
3
3
description: Learn how to create an Azure Dedicated Hosts Group and associate it with Azure Kubernetes Service (AKS)
4
4
services: container-service
5
5
ms.topic: article
6
-
ms.date: 09/13/2022
6
+
ms.date: 12/01/2022
7
7
---
8
8
9
9
# Add Azure Dedicated Host to an Azure Kubernetes Service (AKS) cluster
@@ -28,16 +28,7 @@ The following limitations apply when you integrate Azure Dedicated Host with Azu
28
28
* It isn't supported to update agent pool from host group A to host group B.
29
29
* Using ADH across subscriptions.
30
30
31
-
## Add a Dedicated Host Group to an AKS cluster
32
-
33
-
A host group is a resource that represents a collection of dedicated hosts. You create a host group in a region and an availability zone, and add hosts to it. When planning for high availability, there are more options. You can use one or both of the following options with your dedicated hosts:
34
-
35
-
* Span across multiple availability zones. In this case, you're required to have a host group in each of the zones you wish to use.
36
-
* Span across multiple fault domains, which are mapped to physical racks.
37
-
38
-
In either case, you need to provide the fault domain count for your host group. If you don't want to span fault domains in your group, use a fault domain count of 1.
39
-
40
-
You can also decide to use both availability zones and fault domains.
31
+
## Planning for ADH Capacity on AKS
41
32
42
33
Not all host SKUs are available in all regions, and availability zones. You can list host availability, and any offer restrictions before you start provisioning dedicated hosts.
43
34
@@ -49,6 +40,25 @@ az vm list-skus -l eastus -r hostGroups/hosts -o table
49
40
> First, when using host group, the nodepool fault domain count is always the same as the host group fault domain count. In order to use cluster auto-scaling to work with ADH and AKS, please make sure your host group fault domain count and capacity is enough.
50
41
> Secondly, only change fault domain count from the default of 1 to any other number if you know what they are doing as a misconfiguration could lead to a unscalable configuration.
51
42
43
+
[Determine how many hosts you would need based on the expected VM Utilization](https://learn.microsoft.com/azure/virtual-machines/dedicated-host-general-purpose-skus).
44
+
45
+
Evaluate [host utilization](https://learn.microsoft.com/azure/virtual-machines/dedicated-hosts-how-to?tabs=cli#check-the-status-of-the-host) to determine the number of allocatable VMs by size before you deploy.
46
+
47
+
```azurecli-interactive
48
+
az vm host get-instance-view -g myDHResourceGroup --host-group MyHostGroup --name MyHost
49
+
```
50
+
51
+
## Add a Dedicated Host Group to an AKS cluster
52
+
53
+
A host group is a resource that represents a collection of dedicated hosts. You create a host group in a region and an availability zone, and add hosts to it. When planning for high availability, there are more options. You can use one or both of the following options with your dedicated hosts:
54
+
55
+
* Span across multiple availability zones. In this case, you're required to have a host group in each of the zones you wish to use.
56
+
* Span across multiple fault domains, which are mapped to physical racks.
57
+
58
+
In either case, you need to provide the fault domain count for your host group. If you don't want to span fault domains in your group, use a fault domain count of 1.
59
+
60
+
You can also decide to use both availability zones and fault domains.
61
+
52
62
## Create a Host Group
53
63
54
64
Now create a dedicated host in the host group. In addition to a name for the host, you're required to provide the SKU for the host. Host SKU captures the supported VM series and the hardware generation for your dedicated host.
0 commit comments