Consul Dataplane

Consul Dataplane is a lightweight process that manages Envoy for Consul service mesh workloads, eliminating the need for traditional Consul client agents.

  • Development
  • Network Services
  • Tools & Utilities
Consul Dataplane is a lightweight process that manages Envoy for Consul service mesh workloads, eliminating the need for traditional Consul client agents. It reduces networking complexity by requiring only a single gRPC connection to Consul servers and removes the need to distribute gossip encryption keys during setup. It is designed for operators who want to simplify service mesh configuration and reduce the operational overhead of running a full Consul client on every node.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

62/100 Good

Maintained
100last commit 16 days ago
Popular
3135 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

GitHub stars
35
Open issues
18
Last commit
2026-11-05
Latest release
v2.1.0
License
MPL-2.0
Activity
declining

Checked yesterday - source: GitHub (hashicorp/consul-dataplane)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Put your settings in a config file Create a settings file and start the process with its -config flag so you are not juggling command-line flags. If you skip this, you can forget a needed setting or make accidental changes, and the install can run with the wrong values. source
  • Tell Consul which network cards to ignore If your machine has extra bridge network interfaces with names like br-something, exclude them when you set the client address. Without this, Consul may advertise a local-only IP address, so other machines cannot reach it. source
  • Check the install finished on Kubernetes Run consul-k8s status after installation to see a summary of the deployment, servers, and clients. This helps you catch a half-finished install before you expect services to connect through it. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does Consul Dataplane require a traditional Consul client agent on every node?

No, it is a lightweight process that manages Envoy for Consul service mesh workloads. Its design removes the need to run Consul client agents.

How can I verify that a Consul Kubernetes installation finished correctly?

Run consul-k8s status after installation to see a summary of the deployment, servers, and clients. This helps catch a half-finished install before expecting services to connect.

What HTTP API access issue matters when migrating from Consul Client to Consul Dataplane?

The migration discussion covers reaching the Consul server HTTP API when only port 8300 is exposed.

Answers sourced from developer.hashicorp.com, github.com, stackoverflow.com

Community

Collected 48 days ago - public community threads