Consul client vs. Consul server when accessing KV store

I’m using consul primary for kv store in a kubernetes environment.

Within the cluster I have the two options to access the kV API.

  1. daemonset to provide consul clients - applications will send requests to localhost via consul client.

  2. point application to consul-ui service, which is directly to the consul servers.

It’s my understanding that consul clients would essentially send the request to the consul server regardless.

I’m wondering if there are other advantages to use consul clients for this purpose? (E.g. performance). Or I should just point directly to consul servers?

1 Like

Hi Patrick, I think this question asks the same: Connecting to Consul Cluster - Directly to Remote Server Agent or via Local Client Agent?

Please read the responses there and if you have further questions don’t hesitate to ask!

1 Like