3 ms·
That's not what ingresses are for. Your "docker run" example is equivalent to just accessing the Kubernetes services directly on their host names or IPs. For e
by atombender 6y ago
That's not what ingresses are for.
Your "docker run" example is equivalent to just accessing the Kubernetes services directly on their host names or IPs. For example, with Docker for Desktop, all services of type "LoadBalancer" will automatically get exposed on the host, just like with "docker run".
Ingresses are for setting up HTTP proxying of multiple services on a single host name.
- TuringNYC 6y agoFirstly, I totally agree. Secondly, but it speaks to my initial objection. Not everything can easily be thrown into an adhoc desktop kubernetes setup and it does not make sense for everything -- especially when you have a simple, almost instantaneous alternative way to do it -- docker cli+daemon