Why not? It allows you to route your applications automagically with Kubernetes objects. Instead of writing nginx configurations that do what you want, you can just describe how you want your routing to work. I don't see why that isn't useful.
> k8s just exposes a "managed vm" where you can built stuff like you would do on vmware vApps.
Pods aren't even containers, less VMs. They're namespaces with containers in them.
Secondly, while you can use those pods like VM and boot systemd or whatever in them, that's not really the way you're intended to use Docker. Just to quote an official source:
> It is generally recommended that you separate areas of concern by using one service per container.
Instead of treating Kubernetes like a VM manager, the actual intended way to use it is to treat it like a task manager, like systemd or what have you. The pods are meant to represent individual services, and containers individual processes.
The problem Kubernetes solves is managing applications, not machines. The difference is not merely semantic rambling; it's a paradigm shift.
> You should not use Ingress
Why not? It allows you to route your applications automagically with Kubernetes objects. Instead of writing nginx configurations that do what you want, you can just describe how you want your routing to work. I don't see why that isn't useful.
> k8s just exposes a "managed vm" where you can built stuff like you would do on vmware vApps.
Pods aren't even containers, less VMs. They're namespaces with containers in them.
Secondly, while you can use those pods like VM and boot systemd or whatever in them, that's not really the way you're intended to use Docker. Just to quote an official source:
https://docs.docker.com/config/containers/multi-service_cont...
> It is generally recommended that you separate areas of concern by using one service per container.
Instead of treating Kubernetes like a VM manager, the actual intended way to use it is to treat it like a task manager, like systemd or what have you. The pods are meant to represent individual services, and containers individual processes.
The problem Kubernetes solves is managing applications, not machines. The difference is not merely semantic rambling; it's a paradigm shift.