Open IngwiePhoenix opened 3 months ago
I'm not sure I understand what you mean. As far as I know, the ingress controller already works as a reverse proxy and you just need to setup a Service
resource, include the ingress
directive on your deployment and it'll take care of the rest.
For example, I have a Service
definition pointing to an ExternalName
outside my k8s cluster and the ingress controller handles it with ease.
ExternalName
points to 123.231.123.123 (public ip for another server elsewhere)external.mydomain.name
Hello!
Would it be possible to create a CRD that would facilitate Caddy's excellent reverse proxy feature? If TLS and friends are already set up, it'd be awesome to be able to take advantage of it and reverse proxy to other parts of the network if needed.
Thanks!