It seems to be the month of service mesh releases. This time Kong, creator behind the same way called API Gateway and/or Service Mesh KONG introduced Kuma.
Kuma is a universal open source control-plane for Service Mesh and Microservices that can run and be operated natively across both Kubernetes and VM environments, in order to be easily adopted by every team in the organization.
What's Kuma made of and what's it superpower?
Kuma is written in GO and build on top of the Envoy Proxy. Via CRD it integrated well with Kubernetes while for other virtualization systems it offers a RESTful API. It use L4/L7 traffic to secure, observe, route and enhance connectivity between any service or database.
- Universal Control Plane: Easy to use, distributed, runs anywhere.
- Lightweight Data Plane: To process any traffic, powered by Envoy.
- Automatic: No code changes required in K8s, flexible on VMs.
- Multi-Tenancy: To setup multiple isolated Service Meshes in one cluster and one Control Plane.
- Network Security: Automatic mTLS encryption.
- Traffic Segmentation: With flexible ACL rules.
- Traffic Tracing: Automatic with Zipkin and Jaeger integrations.
- Traffic Metrics: Automatic with Prometheus/Splunk/ELK integrations.
- Proxy Configuration Templating: For advanced users, to configure low-level Envoy configuration.
- Tagging Selectors: To apply sophisticated regional, cloud-specific and team-oriented policies.
- Platform-Agnostic: Support for K8s, VMs, and bare metal.
- Powerful APIM Ingress: Via Kong Gateway integration.