Skip to content

docs: move n4a load balancer topic #538

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 8, 2025
Merged

docs: move n4a load balancer topic #538

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
acb8e51
docs: move n4a load balancer topic
JTorreG May 8, 2025
635420f
Merge branch 'main' into n4a-move-lb-k8s
JTorreG May 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/nginxaas-azure/changelog-archive/changelog-2024.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ To see a list of currently active issues, visit the [Known issues]({{< ref "/ngi

- {{% icon-feature %}} **NGINXaaS Load Balancer for Kubernetes preview release**

You can now use NGINXaaS as an external load balancer to direct traffic into Kubernetes. For details, see the [quickstart]({{< ref "/nginxaas-azure/quickstart/loadbalancer-kubernetes.md" >}}).
You can now use NGINXaaS as an external load balancer to direct traffic into Kubernetes. For details, see the [quickstart]({{< ref "/nginxaas-azure/loadbalancer-kubernetes.md" >}}).

## October 10, 2024

Expand Down
2 changes: 1 addition & 1 deletion content/nginxaas-azure/changelog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ See the [Supported Regions]({{< ref "/nginxaas-azure/overview/overview.md#suppor

- {{% icon-feature %}} **NGINXaaS Load Balancer for Kubernetes is now Generally Available**

NGINXaaS can now be used as an external load balancer to route traffic to workloads running in your Azure Kubernetes Cluster. To learn how to set it up, see the [Quickstart Guide]({{< ref "/nginxaas-azure/quickstart/loadbalancer-kubernetes.md">}}).
NGINXaaS can now be used as an external load balancer to route traffic to workloads running in your Azure Kubernetes Cluster. To learn how to set it up, see the [Quickstart Guide]({{< ref "/nginxaas-azure/loadbalancer-kubernetes.md">}}).

## January 23, 2025

Expand Down
6 changes: 3 additions & 3 deletions ...ure/quickstart/loadbalancer-kubernetes.md → ...nginxaas-azure/loadbalancer-kubernetes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: NGINXaaS Load Balancer for Kubernetes
weight: 250
toc: true
url: /nginxaas/azure/quickstart/loadbalancer-kubernetes/
url: /nginxaas/azure/loadbalancer-kubernetes/
type:
- how-to
---
Expand Down Expand Up @@ -250,7 +250,7 @@ Expose a Kubernetes `Service` to route traffic to your workload. The `Service`
- Choose one of the following `Service` types:
- `NodePort`: To route external traffic into the cluster using a well defined port exposed on each AKS worker node.
- `ClusterIP`: To route traffic to pods directly if you are running an Azure Container Networking Interface (CNI) that lets you expose the pods on the Azure VNET.
- `LoadBalancer`: To route traffic to the cluster's external load balancer. The load balancer routes traffic into the cluster as normal.
- `LoadBalancer`: To route traffic to the cluster's external load balancer. The load balancer routes traffic into the cluster as normal.
- The port name must be formatted as `{{NGINX Context}}-{{NGINX upstream name}}`. For example:
- If the upstream is in the `http` context and named `my-service` then the name is `http-my-service`
- If the upstream is in the `stream` context and named `jet` then the port name is `stream-jet`
Expand All @@ -259,7 +259,7 @@ Expose a Kubernetes `Service` to route traffic to your workload. The `Service`
**NGINX Ingress Controller users**: with v5.0.0 and upwards, if you wish to route traffic from your NGINXaaS deployment to your NGINX Ingress Controller service, please make the following changes to your helm chart values:

- Add `"nginx.com/nginxaas": "nginxaas"` to the NGINX Ingress Controller service annotations.
- Modify the `service.httpPort.name` or `service.httpsPort.name` values to provide the expected port name format, as above.
- Modify the `service.httpPort.name` or `service.httpsPort.name` values to provide the expected port name format, as above.
{{</ note >}}

The following example uses a service of type `NodePort`:
Expand Down
Loading