Ryan Heywood 5167cbc72b Revert "k/ingress-nginx: use PROXY protocol" ... This reverts commit 5131134c1d. Well, that was a rather disappointing result. Turns out, DigitalOcean adds PROXY lines to _all_ connections. I suppose that's to be expected. However, what wasn't expected, was that ingress-nginx would only be capable of handling them for HTTP/S traffic, and not TCP passthrough. For that reason, we actually can't enable PROXY without instead using a sidecar to eat the PROXY line.		2025-06-12 02:49:25 -04:00
..
controller	Revert "k/ingress-nginx: use PROXY protocol"	2025-06-12 02:49:25 -04:00
webhook	k/ingress-nginx: initial commit	2023-05-13 01:31:19 -04:00
kustomization.yaml	Revert "k/ingress-nginx: use PROXY protocol"	2025-06-12 02:49:25 -04:00
namespace.yaml	k/ingress-nginx: initial commit	2023-05-13 01:31:19 -04:00
tcp-services-cm.yaml	k/ingress-nginx: redirect port 22 to forgejo	2023-05-16 01:10:03 -04:00