Open UlaganathanNamachivayam opened 7 years ago
Hi, I'd like to understand why one would run Consul on Kubernetes too please. Could you explain the motivation?
Hello Jackson,
We use Consul because that's what our previous backend guy already uses for service discovery and key-value store before we moved into Kubernetes. I know that Kubernetes has the necessary components built-in to support service discovery and kv store. Isn't it?
On Tue, Jun 27, 2017 at 1:56 PM, Jackson Delahunt notifications@github.com wrote:
Hi, I'd like to understand why one would run Consul on Kubernetes too please. Could you explain the motivation?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/kelseyhightower/consul-on-kubernetes/issues/11#issuecomment-311260682, or mute the thread https://github.com/notifications/unsubscribe-auth/ABhWeUSu1E0mgyLMqKFy0t5mAN3-HGVlks5sIJmYgaJpZM4MlnPE .
-- Eduardo D. Bergavera, Jr. Linux Admin Email: edbergavera@gmail.com OpenID: https://launchpad.net/~edbergavera Github: https://github.com/edbergavera
That is true, and hence our confusion :) I use Consul too for service discovery from the era when this was conventional.
@sabrehagen Consul has other use cases like backing Vault and provide cross cluster service discovery.
I was asked the same questions, and I agree with @kelseyhightower . I like the healthy check feature and I can define my own rules.
Also leader election, distributed locking, persistent KV storage between task runs. It's always nice to have something you can just curl shortcut with a bash script to store a value and fetch/update it later with another curl shortcut.
@kelseyhightower How does it help running consul on kubernetes. How anyone can be able register kubernetes services on to consul and utilize it as service discovery tool over DNS. I am not finding any reference utilizing consul as a service discovery tool for kubernetes.
Kindly share your thoughts/notes if it is a viable solution.