Skip to content
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

Fix and update links in VirtualServer port tutorial #4792

Merged
merged 4 commits into from
Dec 14, 2023
Merged

Fix and update links in VirtualServer port tutorial #4792

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
0ac8b5b
Fix and update links in VirtualServer port tutorial
ADubhlaoich Dec 13, 2023
1349b58
Merge branch 'main' into docs/fix-broken-tutorial-link
ADubhlaoich Dec 13, 2023
55604f4
Merge branch 'main' into docs/fix-broken-tutorial-link
ADubhlaoich Dec 13, 2023
3dc6546
Merge branch 'main' into docs/fix-broken-tutorial-link
ADubhlaoich Dec 13, 2023
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
8 changes: 4 additions & 4 deletions docs/content/tutorials/virtual-server-with-custom-listener-ports.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ toc: true
## Configuring a VirtualServer with custom HTTP and HTTPS listener ports.

VirtualServer can explicitly define custom HTTP and HTTPS listener ports using the `spec.listener.http` and `spec.listener.https` fields.
Each field must reference a valid listener defined by in a [GlobalConfiguration](/nginx-ingress-controller/configuration/global-configuration/globalconfiguration-resource/) resource.
Each field must reference a valid listener defined by in a [GlobalConfiguration]({{< relref "/configuration/global-configuration/globalconfiguration-resource.md" >}}) resource.

## Deploy GlobalConfiguration

Expand Down Expand Up @@ -55,7 +55,7 @@ kubectl apply -f nginx-configuration.yaml
ssl: true
```

1. Follow the [Installation with Helm](/nginx-ingress-controller/installation/installation-with-helm/) instructions to deploy the NGINX Ingress Controller with custom resources enabled.
1. Follow the [Installation with Helm]({{< relref "/installation/installing-nic/installation-with-helm.md" >}}) instructions to deploy the NGINX Ingress Controller with custom resources enabled.

1. Ensure your NodePort or LoadBalancer service is configured to expose the custom listener ports. This is set in the `customPorts` section under `controller.service.customPorts`:

Expand All @@ -82,7 +82,7 @@ kubectl apply -f nginx-configuration.yaml
- -$(POD_NAMESPACE)/nginx-configuration
```

2. Follow the [Installation with Manifests](/nginx-ingress-controller/installation/installation-with-manifests/) instructions to deploy the NGINX Ingress Controller with custom resources enabled.
2. Follow the [Installation with Manifests]({{< relref "/installation/installing-nic/installation-with-manifests.md" >}}) instructions to deploy the NGINX Ingress Controller with custom resources enabled.

3. Ensure your NodePort or LoadBalancer service is configured to expose the custom listener ports. Below is an example yaml configuration using NodePort, which would also apply to a LoadBalancer service:

Expand Down Expand Up @@ -112,7 +112,7 @@ kubectl apply -f nginx-configuration.yaml
{{</tabs>}}

## Deploying VirtualServer with custom listeners
Deploy the example resources in the [custom listeners](/examples/custom-resources/custom-listeners/) folder. This will deploy all required resources, including the VirtualServer.
Deploy the [custom listeners](https://github.com/nginxinc/kubernetes-ingress/tree/v3.3.2/examples/custom-resources/custom-listeners) resources from the repository examples. It includes all required resources, including VirtualServer.

Below is a snippet of the VirtualServer resource that will be deployed:

Expand Down
Loading