github kumahq/kuma v3.0.0
3.0.0

2 hours ago

We are excited to announce Kuma 3.0!

Kuma 3.0 is a major release. It removes the legacy APIs that 2.x deprecated and changes several defaults, so most deployments need changes before the upgrade. Read the upgrade guide before you upgrade.

Notable Changes

Legacy policies removed - the 12 legacy policies (TrafficPermission, TrafficRoute, TrafficLog, TrafficTrace, HealthCheck, CircuitBreaker, Retry, Timeout, RateLimit, FaultInjection, VirtualOutbound and ProxyTemplate) and the legacy ExternalService are gone. Use the Mesh* targetRef policies and MeshExternalService. A new Mesh no longer comes with default policies.

Mesh.mtls removed - use MeshIdentity and MeshTrust for mTLS.

Services without tags - the kuma.io/service tag and the inbound tags are removed from Dataplane, and meshServices is removed from Mesh, so MeshService is always on.

Zone proxies are mesh-scoped only - the standalone ZoneIngress and ZoneEgress resources are removed.

Built-in gateway removed - MeshGateway, MeshGatewayRoute, MeshGatewayInstance and MeshGatewayConfig are gone, together with the north-south Gateway API support.

Control plane modes - standalone mode is removed, and a global control plane must run on Universal.

Data plane - by default, data plane proxies get outbounds only for their reachableBackends, delta xDS is the only xDS protocol, and CoreDNS and the eBPF transparent proxy are removed.

Stricter resources - names of Mesh, Zone, MeshService, MeshExternalService and MeshMultiZoneService must be RFC 1035 labels, fields that are not in the schema are rejected, and control-plane-owned labels are validated.

Multizone - zones authenticate to the global control plane with zone tokens, and zone token secrets are no longer synced to zones.

Performance - many KDS, xDS and API server performance improvements.

Changelog

Don't miss a new kuma release

NewReleases is sending notifications on new releases.