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: content/nginxaas-azure/loadbalancer-kubernetes.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -300,7 +300,7 @@ spec:
300
300
301
301
### Multiple AKS clusters
302
302
303
-
A single NGINXaaS deployment can direct trafifc to multiple AKS clusters. Each AKS cluster needs its own copy of NLK installed and connected to NGINXaaS.
303
+
A single NGINXaaS deployment can direct traffic to multiple AKS clusters. Each AKS cluster needs its own copy of NLK installed and connected to NGINXaaS.
304
304
305
305
```mermaid
306
306
flowchart TB
@@ -351,7 +351,7 @@ flowchart TB
351
351
352
352
Multiple NLK controllers can be installed in the same AKS cluster to update separate NGINXaaS deployments.
353
353
354
-
Each NLK needs a unique helm release name and needs a unique helm value for `nlk.config.serviceAnnotationMatch`. Each NLK will only watch services that have the matching annotation.
354
+
Each NLK needs a unique helm release name and needs a unique helm value for `nlk.config.serviceAnnotationMatch`. Each NLK will only watch services that have the matching annotation.
355
355
356
356
{{<note>}}
357
357
@@ -374,7 +374,7 @@ The logs can be made more verbose by setting the Helm value `nlk.config.logLevel
374
374
375
375
NGINXaaS supports exporting dynamic upstream update logs to an Azure Storage account or to a Log Analytics workspace.
376
376
377
-
To setup logging:
377
+
To set up logging:
378
378
379
379
1. Select **Diagnostic settings** under **Monitoring**.
0 commit comments