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.

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

added few tips for TCP/UDP Load Balancing #5117

Merged
merged 6 commits into from
Feb 26, 2024
Merged
Changes from 1 commit
Commits
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
4 changes: 4 additions & 0 deletions examples/custom-resources/basic-tcp-udp/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,10 @@ server pods.
- As part of Step 2 of those instructions, make sure to deploy the GlobalConfiguration resource and configure the
Ingress Controller to use it.
- Expose port 5353 of the Ingress Controller both for TCP and UDP traffic.
(Make use of [controller.customPorts](https://docs.nginx.com/nginx-ingress-controller/installation/installing-nic/installation-with-helm/)
ssrahul96 marked this conversation as resolved.
Show resolved Hide resolved
and [controller.service.customPorts](https://docs.nginx.com/nginx-ingress-controller/installation/installing-nic/installation-with-helm/)
ssrahul96 marked this conversation as resolved.
Show resolved Hide resolved
for exposing Pod and LoadBalancer Port(s) respectively)

1. Save the public IP address of the Ingress Controller into a shell variable:

```console
Expand Down
Loading