kuma
The official Kuma image — the CNCF service mesh control plane and data plane built on Envoy, providing traffic management, mTLS, and observability across Kubernetes and VMs.
What is Kuma?
The Kuma images package Kuma, a CNCF service mesh built on the Envoy proxy that manages traffic, security, and observability for services running on Kubernetes and virtual machines. The control plane, kuma-cp, distributes policy to data plane proxies, which are managed with kuma-dp sidecars, and it supports mutual TLS, traffic routing, fault injection, rate limiting, retries, and multi-zone deployments. Other images in the project include the CLI and the sidecar init tooling. Kuma is used by platform and networking teams that need consistent zero-trust networking and traffic policy across clusters and environments, with reproducible version-pinned images.
What is Echo's Kuma image?
Echo's Kuma image is a hardened build of Kuma on Echo's hardened base. Echo images are designed to be a drop-in replacement: swap the image reference in your Dockerfile or deployment manifest and CVEs go to zero without disrupting your mesh and policy resources, mTLS settings, zone configuration, and sidecar injection. Every image is tested across clouds, image use cases, and deployment targets. Echo ships every image in two variants:
- Distroless variant — optimized for runtime use, with the smallest possible attack surface
- Default variant — includes essential build tools, package managers, and shells for teams that need operational access
For production Kuma deployments, the distroless variant keeps all runtime operations — policy distribution, certificate issuance, Envoy configuration, and traffic management — fully intact while minimizing exposure; the default variant suits platform and networking teams that need shell access for debugging policies, running kumactl, or inspecting proxy configuration.
What is the difference between Echo's Kuma image and the public Kuma image?
Public Kuma images ship on bases that include OS-level tooling convenient for development but which contribute CVEs that accumulate on a service mesh control plane and proxy used in production. Kuma images run continuously with access to mesh certificates, traffic policies, and visibility into service-to-service traffic. OS-level CVEs in the base image — particularly in libraries such as openssl, zlib, and libc, along with Envoy and Go runtime dependencies — create exploitable paths that bypass application-layer controls entirely, allowing attackers to move from a network-reachable service to host-level access. For teams running Kuma across many environments, the image is also a steady source of scanner noise in the CI pipeline — every package in the base becomes a finding your security team must triage, even when none of it is reachable from the service. Echo's build retains everything Kuma needs for policy distribution, certificate issuance, Envoy configuration, and traffic management while removing the packages that don't belong in a production Kuma service mesh control plane and proxy. As we covered in our post on how to protect your company from software supply chain attacks, long-running services that hold sensitive data and listen on the network are among the widest attack surfaces in the container stack. Echo commits to a 7-day SLA for critical and high severity vulnerabilities, and 10 days for medium, low, and unknown — with vulnerabilities triaged within 24 hours. Echo images are recognized by all major scanners and mirrored to all major registries, so they fit into existing pipelines without changing your registry, scanner, or runtime tooling.
FAQ
Can I replace my Kuma image with Echo's Kuma image?
Yes. Echo's Kuma image is a drop-in replacement. Update the FROM line in your Dockerfile and your workloads keep running. Mesh and policy resources, mTLS configuration, sidecar injection, multi-zone setups, and Envoy proxy behavior all continue to work without changes to your manifests or application code.
Is Echo's Kuma image FIPS-validated?
Yes. Echo's FIPS-validated images use cryptographic modules with an active FIPS 140-3 CMVP certificate, making them fit for federal use — unlike FIPS-compliant images that haven't been validated. This matters for teams running Kuma workloads inside FedRAMP boundaries, where a service mesh control plane and proxy that issues workload identities and enforces traffic policy for every service in the mesh must meet cryptographic requirements across the full stack — including the OpenSSL and TLS libraries bundled with the Kuma image.
What is Echo's vulnerability management SLA on the Kuma image?
Echo commits to a 7-day SLA for critical and high severity vulnerabilities, and 10 days for medium, low, and unknown — with vulnerabilities triaged within 24 hours. Patches are mirrored automatically into your private registry so you're always running a clean version — critical for a long-running service that holds mesh certificates, traffic policies, and visibility into service-to-service traffic and is reachable over the network.
Is Echo's Kuma image distroless?
Echo ships every image in two variants: a distroless variant optimized for runtime use, and a default variant that includes essential build tools, package managers, and shells. For production Kuma deployments, the distroless variant is the leaner, more secure choice; for platform and networking teams that need shell access for debugging policies, running kumactl, or inspecting proxy configuration, the default variant is the right fit.
How does Echo achieve such a drastic CVE reduction in Kuma?
Echo's Kuma image is built from source with only the absolute essentials needed to run the Kuma service mesh control plane and proxy, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the Kuma version your applications and their dependencies are certified against — avoiding a disruptive upgrade forced purely by OS-level vulnerabilities in the base image rather than by your own requirements.
Will Echo's Kuma image help us achieve FedRAMP?
Yes. The hard parts of FedRAMP — managing vulnerabilities, applying fixes, and using FIPS-validated cryptography — are baked into Echo images, including STIG-hardened configuration and ConMon/POA&M-ready reporting. For platform and networking teams running Kuma under an ATO — whether that's zero-trust service-to-service encryption, multi-cluster traffic policy, or mesh observability — Echo's hardened Kuma image keeps the service mesh control plane and proxy layer in-boundary and compliant without requiring custom hardening scripts or manual base image patching between compliance cycles.
.avif)