What are advantages use consul in kubernetes (use cases without Service Mesh and consul connect)?
We are looking only use case - Service Discovery and Health Checking + KV
Not included use cases:
- Network Infrastructure Automation
- Multi-Platform Service Mesh
I read official comparison kubernetes vs consul and I can’t understand what are advantages of using consul clients + servers. Let’s take a look of what we have with consul and kubernetes:
Service discovery: Consul – Yes, Kubernetes – Yes
Health Checking: Consul – Yes, Kubernetes – Yes
Key/Value Storage: Consul – Yes. Kubernetes – Yes, but maybe little bit less flexible out of the box than in consul
If I’m correct install consul to kubernetes (no valt, no consul connect) make no sense if all application works in the k8s?
Maybe only if there are applications that works outside the k8s and connect them to consul into kuberenetes for 1-3 purposes that described above.
But now it’s little bit unclear to understand how applications outside k8s cluster (that register in k8s consul) will be communicate with outer app in k8s because ip pods network is private in k8s is private with no directly access outside by-default.
If it can be possible so we can achieve Service Discovery K8S Consul + Service Discovery outside K8S into one big connected SD or maybe more and included Health Checking and KV on both sides