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/use-group-managed-service-accounts.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,9 +54,7 @@ Your domain controller needs to be configured through DNS so it's reachable by t
54
54
55
55
## Optional: Configure more than one DNS server
56
56
57
-
If you want to configure more than one DNS server for Windows GMSA in your AKS cluster, you should not specify `--gmsa-dns-server` or `v--gmsa-root-domain-name`as described in the instructions below.
58
-
59
-
Instead, you should add multiple DNS servers in the vnet by selecting Custom DNS and adding multiple DNS servers.
57
+
If you want to configure more than one DNS server for Windows GMSA in your AKS cluster, don't specify `--gmsa-dns-server`or `v--gmsa-root-domain-name`. Instead, you can add multiple DNS servers in the vnet by selecting Custom DNS and adding the DNS servers
60
58
61
59
## Optional: Use your own kubelet identity for your cluster
Copy file name to clipboardExpand all lines: articles/aks/windows-faq.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,7 +69,7 @@ Yes. For the implications of making a change and the options that are available,
69
69
70
70
## What is the default TCP timeout in Windows OS?
71
71
72
-
The default TCP timeout in Windows OS is 4 minutes. This value is not configurable. When a user's application uses a longer timeout, the TCP connections between different containers in the same node will be closed after 4 minutes.
72
+
The default TCP timeout in Windows OS is 4 minutes. This value isn't configurable. When an application uses a longer timeout, the TCP connections between different containers in the same node close after four minutes.
73
73
74
74
## Why am I seeing an error when I try to create a new Windows agent pool?
75
75
@@ -84,9 +84,9 @@ To fix this error:
84
84
1. Move Windows pods from existing Windows agent pools to new Windows agent pools.
85
85
1. Delete old Windows agent pools.
86
86
87
-
## Why am I seeing an error when I try to deploy Windows pods
87
+
## Why am I seeing an error when I try to deploy Windows pods?
88
88
89
-
If you have specified a value in `--max-pods`that is less than the number of pods you want to create, you may see the error "No available addresses".
89
+
If you specify a value in `--max-pods` less than the number of pods you want to create, you may see the `No available addresses` error.
90
90
91
91
To fix this error, use the `az aks nodepool add` command with a high enough `--max-pods` value:
92
92
@@ -97,7 +97,7 @@ az aks nodepool add \
97
97
--name $NODEPOOL_NAME \
98
98
--max-pods 3
99
99
```
100
-
See [documentation](https://learn.microsoft.com/cli/azure/aks/nodepool?view=azure-cli-latest#az-aks-nodepool-add:~:text=for%20system%20nodepool.-,%2D%2Dmax%2Dpods%20%2Dm,-The%20maximum%20number) on `--max-pods` for more details.
100
+
For more details, see the [`--max-pods`documentation](https://learn.microsoft.com/cli/azure/aks/nodepool?view=azure-cli-latest#az-aks-nodepool-add:~:text=for%20system%20nodepool.-,%2D%2Dmax%2Dpods%20%2Dm,-The%20maximum%20number).
101
101
102
102
## Why is there an unexpected user named "sshd" on my VM node?
103
103
@@ -178,7 +178,7 @@ A cluster with Windows nodes can have approximately 500 services (sometimes less
178
178
179
179
When external traffic policy on a Service is configured as Cluster, the traffic undergoes an additional Source NAT on the node which also results in reservation of a port from the TCPIP dynamic port pool. This port pool is a limited resource (~16K ports by default) and many active connections to a Service(s) can lead to dynamic port pool exhaustion resulting in connection drops.
180
180
181
-
If the Kubernetes Service is configured with External Traffic Policy set to “Local”, port exhaustion problems are not likely to occur at 500 services.
181
+
If the Kubernetes Service is configured with External Traffic Policy set to “Local”, port exhaustion problems aren't likely to occur at 500 services.
182
182
183
183
## Can I use Azure Hybrid Benefit with Windows nodes?
0 commit comments