Hi,
It would be possible to run Consul in an agentless setup like this,
but it's definitely not recommended.
The Consul agent is relatively lightweight and is pretty core to
Consul architecture. It does edge-triggered updates to the Consul
servers only when health check statuses change, so scales much better
than a centralized health checking approach. Also, the health of the
nodes running the agents are automatically checked by Consul's gossip
protocol, so if an agent goes offline the other agents will quickly
detect that and report it to the servers, which will mark all of its
services unhealthy via the automatic "serfHealth" check. Gossip also
allows the agents to find a healthy Consul server to talk to, so your
application doesn't need to discover the Consul servers (it can just
be hard-coded to talk to its local agent at 127.0.0.1).
This recent talk walks through this in more detail -
https://www.youtube.com/watch?v=tzk2HaOZ5nY.
Hope that helps!
-- James
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
>
https://www.hashicorp.com/community-guidelines.html. Behavior in violation
> of those guidelines may result in your removal from this mailing list.
>
> GitHub Issues:
https://github.com/hashicorp/consul/issues
> IRC: #consul on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Consul" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
consul-tool...@googlegroups.com.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/consul-tool/04116b93-109c-4619-9d45-ac0848d01f8d%40googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.