Skip to content

Commit cd38e31

Browse files
v-regandownerv-regandowner
authored
Merge pull request #221397 from khdownie/kendownie-aks-28630
standardize preview feature flag instrux
2 parents 5fa9895 + 4603027 commit cd38e31

18 files changed

+388
-249
lines changed

‎articles/aks/api-server-vnet-integration.md

Lines changed: 21 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,6 @@ ms.custom: references_regions
1212

1313
An Azure Kubernetes Service (AKS) cluster configured with API Server VNet Integration (Preview) projects the API server endpoint directly into a delegated subnet in the VNet where AKS is deployed. API Server VNet Integartion enables network communication between the API server and the cluster nodes without requiring a private link or tunnel. The API server is available behind an Internal Load Balancer VIP in the delegated subnet, which the nodes are configured to utilize. By using API Server VNet Integration, you can ensure network traffic between your API server and your node pools remains on the private network only.
1414

15-
[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
16-
1715
## API server connectivity
1816

1917
The control plane or API server is in an Azure Kubernetes Service (AKS)-managed Azure subscription. A customer's cluster or node pool is in the customer's subscription. The server and the virtual machines that make up the cluster nodes can communicate with each other through the API server VIP and pod IPs that are projected into the delegated subnet.
@@ -31,33 +29,37 @@ API Server VNet Integration is available in all global Azure regions except the
3129
* Azure CLI with aks-preview extension 0.5.97 or later.
3230
* If using ARM or the REST API, the AKS API version must be 2022-04-02-preview or later.
3331

34-
### Install the aks-preview CLI extension
32+
## Install the aks-preview Azure CLI extension
3533

36-
```azurecli-interactive
37-
# Install the aks-preview extension
34+
[!INCLUDE [preview features callout](includes/preview/preview-callout.md)]
35+
36+
To install the aks-preview extension, run the following command:
37+
38+
```azurecli
3839
az extension add --name aks-preview
40+
```
41+
42+
Run the following command to update to the latest version of the extension released:
3943

40-
# Update the extension to make sure you have the latest version installed
44+
```azurecli
4145
az extension update --name aks-preview
4246
```
4347

44-
### Register the `EnableAPIServerVnetIntegrationPreview` preview feature
45-
46-
To create an AKS cluster with API Server VNet Integration, you must enable the `EnableAPIServerVnetIntegrationPreview` feature flag on your subscription.
48+
## Register the 'EnableAPIServerVnetIntegrationPreview' feature flag
4749

48-
Register the `EnableAPIServerVnetIntegrationPreview` feature flag by using the `az feature register` command, as shown in the following example:
50+
Register the `EnableAPIServerVnetIntegrationPreview` feature flag by using the [az feature register][az-feature-register] command, as shown in the following example:
4951

5052
```azurecli-interactive
5153
az feature register --namespace "Microsoft.ContainerService" --name "EnableAPIServerVnetIntegrationPreview"
5254
```
5355

54-
It takes a few minutes for the status to show *Registered*. Verify the registration status by using the `az feature list` command:
56+
It takes a few minutes for the status to show *Registered*. Verify the registration status by using the [az feature show][az-feature-show] command:
5557

5658
```azurecli-interactive
57-
az feature list -o table --query "[?contains(name, 'Microsoft.ContainerService/EnableAPIServerVnetIntegrationPreview')].{Name:name,State:properties.state}"
59+
az feature show --namespace "Microsoft.ContainerService" --name "EnableAPIServerVnetIntegrationPreview"
5860
```
5961

60-
When the feature has been registered, refresh the registration of the *Microsoft.ContainerService* resource provider by using the `az provider register` command:
62+
When the status reflects *Registered*, refresh the registration of the *Microsoft.ContainerService* resource provider by using the [az provider register][az-provider-register] command:
6163

6264
```azurecli-interactive
6365
az provider register --namespace Microsoft.ContainerService
@@ -227,11 +229,12 @@ az aks update -n <cluster-name> \
227229
For associated best practices, see [Best practices for network connectivity and security in AKS][operator-best-practices-network].
228230

229231
<!-- LINKS - internal -->
230-
[az-provider-register]: /cli/azure/provider#az_provider_register
231-
[az-feature-register]: /cli/azure/feature#az_feature_register
232-
[az-feature-list]: /cli/azure/feature#az_feature_list
233-
[az-extension-add]: /cli/azure/extension#az_extension_add
234-
[az-extension-update]: /cli/azure/extension#az_extension_update
232+
[az-provider-register]: /cli/azure/provider#az-provider-register
233+
[az-feature-register]: /cli/azure/feature#az-feature-register
234+
[az-feature-list]: /cli/azure/feature#az-feature-list
235+
[az-feature-show]: /cli/azure/feature#az-feature-show
236+
[az-extension-add]: /cli/azure/extension#az-extension-add
237+
[az-extension-update]: /cli/azure/extension#az-extension-update
235238
[private-link-service]: ../private-link/private-link-service-overview.md#limitations
236239
[private-endpoint-service]: ../private-link/private-endpoint-overview.md
237240
[virtual-network-peering]: ../virtual-network/virtual-network-peering-overview.md

‎articles/aks/azure-cni-overlay.md

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -115,13 +115,13 @@ Register the `AzureOverlayPreview` feature flag by using the [az feature registe
115115
az feature register --namespace "Microsoft.ContainerService" --name "AzureOverlayPreview"
116116
```
117117

118-
It takes a few minutes for the status to show *Registered*. Verify the registration status by using the [az feature list][az-feature-list] command:
118+
It takes a few minutes for the status to show *Registered*. Verify the registration status by using the [az feature show][az-feature-show] command:
119119

120120
```azurecli-interactive
121-
az feature list -o table --query "[?contains(name, 'Microsoft.ContainerService/AzureOverlayPreview')].{Name:name,State:properties.state}"
121+
az feature show --namespace "Microsoft.ContainerService" --name "AzureOverlayPreview"
122122
```
123123

124-
When ready, refresh the registration of the *Microsoft.ContainerService* resource provider by using the [az provider register][az-provider-register] command:
124+
When the status reflects *Registered*, refresh the registration of the *Microsoft.ContainerService* resource provider by using the [az provider register][az-provider-register] command:
125125

126126
```azurecli-interactive
127127
az provider register --namespace Microsoft.ContainerService
@@ -157,4 +157,9 @@ The following steps create a new virtual network with a subnet for the cluster n
157157
158158
## Next steps
159159
160-
To learn how to utilize AKS with your own Container Network Interface (CNI) plugin, see [Bring your own Container Network Interface (CNI) plugin](use-byo-cni.md).
160+
To learn how to utilize AKS with your own Container Network Interface (CNI) plugin, see [Bring your own Container Network Interface (CNI) plugin](use-byo-cni.md).
161+
162+
<!-- LINKS - internal -->
163+
[az-provider-register]: /cli/azure/provider#az-provider-register
164+
[az-feature-register]: /cli/azure/feature#az-feature-register
165+
[az-feature-show]: /cli/azure/feature#az-feature-show

‎articles/aks/azure-cni-powered-by-cilium.md

Lines changed: 18 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,6 @@ By making use of eBPF programs loaded into the Linux kernel and a more efficient
1919
- Better observability of cluster traffic
2020
- Support for larger clusters (more nodes, pods, and services)
2121

22-
[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
23-
2422
## IP Address Management (IPAM) with Azure CNI Powered by Cilium
2523

2624
Azure CNI Powered by Cilium can be deployed using two different methods for assigning pod IPs:
@@ -55,33 +53,37 @@ Azure CNI powered by Cilium currently has the following limitations:
5553
* Azure CLI with aks-preview extension 0.5.109 or later.
5654
* If using ARM templates or the REST API, the AKS API version must be 2022-09-02-preview or later.
5755

58-
### Install the aks-preview CLI extension
56+
## Install the aks-preview Azure CLI extension
5957

60-
```azurecli-interactive
61-
# Install the aks-preview extension
58+
[!INCLUDE [preview features callout](includes/preview/preview-callout.md)]
59+
60+
To install the aks-preview extension, run the following command:
61+
62+
```azurecli
6263
az extension add --name aks-preview
64+
```
65+
66+
Run the following command to update to the latest version of the extension released:
6367

64-
# Update the extension to make sure you have the latest version installed
68+
```azurecli
6569
az extension update --name aks-preview
6670
```
6771

68-
### Register the `CiliumDataplanePreview` preview feature
69-
70-
To create an AKS cluster with Azure CNI powered by Cilium, you must enable the `CiliumDataplanePreview` feature flag on your subscription.
72+
## Register the 'CiliumDataplanePreview' feature flag
7173

72-
Register the `CiliumDataplanePreview` feature flag by using the `az feature register` command, as shown in the following example:
74+
Register the `CiliumDataplanePreview` feature flag by using the [az feature register][az-feature-register] command, as shown in the following example:
7375

7476
```azurecli-interactive
7577
az feature register --namespace "Microsoft.ContainerService" --name "CiliumDataplanePreview"
7678
```
7779

78-
It takes a few minutes for the status to show *Registered*. Verify the registration status by using the `az feature list` command:
80+
It takes a few minutes for the status to show *Registered*. Verify the registration status by using the [az feature show][az-feature-show] command:
7981

8082
```azurecli-interactive
81-
az feature list -o table --query "[?contains(name, 'Microsoft.ContainerService/CiliumDataplanePreview')].{Name:name,State:properties.state}"
83+
az feature show --namespace "Microsoft.ContainerService" --name "CiliumDataplanePreview"
8284
```
8385

84-
When the feature has been registered, refresh the registration of the *Microsoft.ContainerService* resource provider by using the `az provider register` command:
86+
When the status reflects *Registered*, refresh the registration of the *Microsoft.ContainerService* resource provider by using the [az provider register][az-provider-register] command:
8587

8688
```azurecli-interactive
8789
az provider register --namespace Microsoft.ContainerService
@@ -174,3 +176,6 @@ Learn more about networking in AKS in the following articles:
174176
[aks-ingress-static-tls]: ingress-static-ip.md
175177
[aks-http-app-routing]: http-application-routing.md
176178
[aks-ingress-internal]: ingress-internal-ip.md
179+
[az-provider-register]: /cli/azure/provider#az-provider-register
180+
[az-feature-register]: /cli/azure/feature#az-feature-register
181+
[az-feature-show]: /cli/azure/feature#az-feature-show

‎articles/aks/configure-kube-proxy.md

Lines changed: 19 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -20,40 +20,42 @@ author: phealy
2020

2121
The AKS managed `kube-proxy` DaemonSet can also be disabled entirely if that is desired to support [bring-your-own CNI][aks-byo-cni].
2222

23-
[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
24-
2523
## Prerequisites
2624

2725
* Azure CLI with aks-preview extension 0.5.105 or later.
2826
* If using ARM or the REST API, the AKS API version must be 2022-08-02-preview or later.
2927

30-
### Install the aks-preview CLI extension
28+
## Install the aks-preview Azure CLI extension
3129

32-
```azurecli-interactive
33-
# Install the aks-preview extension
30+
[!INCLUDE [preview features callout](includes/preview/preview-callout.md)]
31+
32+
To install the aks-preview extension, run the following command:
33+
34+
```azurecli
3435
az extension add --name aks-preview
36+
```
37+
38+
Run the following command to update to the latest version of the extension released:
3539

36-
# Update the extension to make sure you have the latest version installed
40+
```azurecli
3741
az extension update --name aks-preview
3842
```
3943

40-
### Register the `KubeProxyConfigurationPreview` preview feature
41-
42-
To create an AKS cluster with custom `kube-proxy` configuration, you must enable the `KubeProxyConfigurationPreview` feature flag on your subscription.
44+
## Register the 'KubeProxyConfigurationPreview' feature flag
4345

44-
Register the `KubeProxyConfigurationPreview` feature flag by using the `az feature register` command, as shown in the following example:
46+
Register the `KubeProxyConfigurationPreview` feature flag by using the [az feature register][az-feature-register] command, as shown in the following example:
4547

4648
```azurecli-interactive
4749
az feature register --namespace "Microsoft.ContainerService" --name "KubeProxyConfigurationPreview"
4850
```
4951

50-
It takes a few minutes for the status to show *Registered*. Verify the registration status by using the `az feature list` command:
52+
It takes a few minutes for the status to show *Registered*. Verify the registration status by using the [az feature show][az-feature-show] command:
5153

5254
```azurecli-interactive
53-
az feature list -o table --query "[?contains(name, 'Microsoft.ContainerService/KubeProxyConfigurationPreview')].{Name:name,State:properties.state}"
55+
az feature show --namespace "Microsoft.ContainerService" --name "KubeProxyConfigurationPreview"
5456
```
5557

56-
When the feature has been registered, refresh the registration of the *Microsoft.ContainerService* resource provider by using the `az provider register` command:
58+
When the status reflects *Registered*, refresh the registration of the *Microsoft.ContainerService* resource provider by using the [az provider register][az-provider-register] command:
5759

5860
```azurecli-interactive
5961
az provider register --namespace Microsoft.ContainerService
@@ -135,4 +137,7 @@ Learn more about Kubernetes services at the [Kubernetes services documentation][
135137
[aks-schema-kubeproxyconfig]: /azure/templates/microsoft.containerservice/managedclusters?pivots=deployment-language-bicep#containerservicenetworkprofilekubeproxyconfig
136138

137139
<!-- LINKS - Internal -->
138-
[aks-byo-cni]: use-byo-cni.md
140+
[aks-byo-cni]: use-byo-cni.md
141+
[az-provider-register]: /cli/azure/provider#az-provider-register
142+
[az-feature-register]: /cli/azure/feature#az-feature-register
143+
[az-feature-show]: /cli/azure/feature#az-feature-show

‎articles/aks/configure-kubenet-dual-stack.md

Lines changed: 23 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,6 @@ AKS clusters can now be deployed in a dual-stack (using both IPv4 and IPv6 addre
1212

1313
This article shows you how to use dual-stack networking with an AKS cluster. For more information on network options and considerations, see [Network concepts for Kubernetes and AKS][aks-network-concepts].
1414

15-
[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
16-
1715
## Limitations
1816
> [!NOTE]
1917
> Dual-stack kubenet networking is currently not available in sovereign clouds. This note will be removed when rollout is complete.
@@ -34,36 +32,40 @@ This article shows you how to use dual-stack networking with an AKS cluster. For
3432
* Azure CLI with the `aks-preview` extension 0.5.48 or newer.
3533
* If using Azure Resource Manager templates, schema version 2021-10-01 is required.
3634

37-
### Register the `AKS-EnableDualStack` preview feature
35+
## Install the aks-preview Azure CLI extension
3836

39-
To create an AKS dual-stack cluster, you must enable the `AKS-EnableDualStack` feature flag on your subscription.
37+
[!INCLUDE [preview features callout](includes/preview/preview-callout.md)]
4038

41-
Register the `AKS-EnableDualStack` feature flag by using the `az feature register` command, as shown in the following example:
39+
To install the aks-preview extension, run the following command:
4240

43-
```azurecli-interactive
44-
az feature register --namespace "Microsoft.ContainerService" --name "AKS-EnableDualStack"
41+
```azurecli
42+
az extension add --name aks-preview
4543
```
4644

47-
It takes a few minutes for the status to show *Registered*. Verify the registration status by using the `az feature list` command:
45+
Run the following command to update to the latest version of the extension released:
4846

49-
```azurecli-interactive
50-
az feature list -o table --query "[?contains(name, 'Microsoft.ContainerService/AKS-EnableDualStack')].{Name:name,State:properties.state}"
47+
```azurecli
48+
az extension update --name aks-preview
5149
```
5250

53-
When ready, refresh the registration of the *Microsoft.ContainerService* resource provider by using the `az provider register` command:
51+
## Register the 'AKS-EnableDualStack' feature flag
52+
53+
Register the `AKS-EnableDualStack` feature flag by using the [az feature register][az-feature-register] command, as shown in the following example:
5454

5555
```azurecli-interactive
56-
az provider register --namespace Microsoft.ContainerService
56+
az feature register --namespace "Microsoft.ContainerService" --name "AKS-EnableDualStack"
5757
```
5858

59-
### Install the aks-preview CLI extension
59+
It takes a few minutes for the status to show *Registered*. Verify the registration status by using the [az feature show][az-feature-show] command:
6060

6161
```azurecli-interactive
62-
# Install the aks-preview extension
63-
az extension add --name aks-preview
62+
az feature show --namespace "Microsoft.ContainerService" --name "AKS-EnableDualStack"
63+
```
6464

65-
# Update the extension to make sure you have the latest version installed
66-
az extension update --name aks-preview
65+
When the status reflects *Registered*, refresh the registration of the *Microsoft.ContainerService* resource provider by using the [az provider register][az-provider-register] command:
66+
67+
```azurecli-interactive
68+
az provider register --namespace Microsoft.ContainerService
6769
```
6870

6971
## Overview of dual-stack networking in Kubernetes
@@ -400,4 +402,7 @@ curl -s "http://[${SERVICE_IP}]" | head -n5
400402
[express-route]: ../expressroute/expressroute-introduction.md
401403
[network-comparisons]: concepts-network.md#compare-network-models
402404
[custom-route-table]: ../virtual-network/manage-route-table.md
403-
[user-assigned managed identity]: use-managed-identity.md#bring-your-own-control-plane-mi
405+
[user-assigned managed identity]: use-managed-identity.md#bring-your-own-control-plane-mi
406+
[az-provider-register]: /cli/azure/provider#az-provider-register
407+
[az-feature-register]: /cli/azure/feature#az-feature-register
408+
[az-feature-show]: /cli/azure/feature#az-feature-show

0 commit comments

Comments
 (0)