Skip to content

Commit 263d736

Browse files
authored
Merge pull request #107010 from zr-msft/zr-aks-1649702-network-contrib
[AKS] changed role in SP assignment
2 parents 7849cfe + 7610fb2 commit 263d736

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/aks/static-ip.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Use a static IP address and DNS label with the Azure Kubernetes Service (
33
description: Learn how to create and use a static IP address with the Azure Kubernetes Service (AKS) load balancer.
44
services: container-service
55
ms.topic: article
6-
ms.date: 11/06/2019
6+
ms.date: 03/09/2020
77

88

99
#Customer intent: As a cluster operator or developer, I want to create and manage static IP address resources in Azure that I can use beyond the lifecycle of an individual Kubernetes service deployed in an AKS cluster.
@@ -65,7 +65,7 @@ Before creating a service, ensure the service principal used by the AKS cluster
6565
```azurecli-interactive
6666
az role assignment create \
6767
--assignee <SP Client ID> \
68-
--role "Contributor" \
68+
--role "Network Contributor" \
6969
--scope /subscriptions/<subscription id>/resourceGroups/<resource group name>
7070
```
7171

@@ -95,7 +95,7 @@ kubectl apply -f load-balancer-service.yaml
9595

9696
## Apply a DNS label to the service
9797

98-
If your service is using a dynamic or static public IP address, you can use the service annotation `service.beta.kubernetes.io/azure-dns-label-name` to set a public-facing DNS label. This publishes a fully qualified domain name for your service using Azure's public DNS servers and top-level domain. The annotation value must be unique within the Azure location, so its recommended to use a sufficiently qualified label.
98+
If your service is using a dynamic or static public IP address, you can use the service annotation `service.beta.kubernetes.io/azure-dns-label-name` to set a public-facing DNS label. This publishes a fully qualified domain name for your service using Azure's public DNS servers and top-level domain. The annotation value must be unique within the Azure location, so it's recommended to use a sufficiently qualified label.
9999

100100
Azure will then automatically append a default subnet, such as `<location>.cloudapp.azure.com` (where location is the region you selected), to the name you provide, to create the fully qualified DNS name. For example:
101101

0 commit comments

Comments
 (0)