A new Kuma
release that brings in many highly-requested features:
- support for ingress traffic into the service mesh - it is now possible to re-use
existing, feature-richAPI Gateway
solutions at the front doors of
your service mesh.
E.g., check out our instructions how to leverageKuma
and Kong together. Or, if you're a hands-on kind of person, play with our demos for kubernetes and universal. - access to Prometheus metrics collected by individual dataplanes (Envoys) -
as a user, you only need to enablePrometheus
metrics as part of yourMesh
policy,
and that's it - every dataplane (Envoy) will automatically make its metrics available for scraping. Read more about it in the docs. - native integration with Prometheus auto-discovery - be it
kubernetes
oruniversal
(😮),Prometheus
will automatically find all dataplanes in your mesh and scrape metrics out of them. Sounds interesting? See our docs and play with our demos for kubernetes and universal. - brand new Kuma GUI - following the very first preview release,
Kuma GUI
have been significantly overhauled to include more features, like support for every Kuma policy. Read more about it in the docs, see it live as part of our demos for kubernetes and universal.
Download Kuma 0.3.2 and run it now:
CHANGELOG:
Changes:
- feature: enable proxying of Kuma REST API via Kuma GUI
#542 - feature: add a brand new version of Kuma GUI
#538 - feature: add support for
MonitoringAssignment
s with arbitraryTarget
labels (rather than only__address__
) tokuma-prometheus-sd
#540 - feature: on
kuma-prometheus-sd
start-up, check write permissions on the output dir
#539 - feature: implement MADS xDS client and integrate
kuma-prometheus-sd
withPrometheus
viafile_sd
discovery
#537 - feature: add configuration options to
kuma-prometheus-sd run
#536 - feature: add
kuma-prometheus-sd
binary
#535 - feature: advertise MonitoringAssignment server via API Catalog
#534 - feature: generate MonitoringAssignment for each Dataplane in a Mesh
#532 - feature: add a Monitoring Assignment Discovery Service (MADS) server
#531 - feature: add a generic watchdog for xDS streams
#530 - feature: add a generic versioner for xDS Snapshots
#529 - feature: add a custom version of SnapshotCache that supports arbitrary xDS resources
#528 - feature: add proto definition for Monitoring Assignment Discovery Service (MADS)
#525 - feature: enable Envoy Admin API by default with an option to opt out
#523 - feature: add integration with Prometheus on K8S
#524 - feature: redirect requests to /api path on GUI server to API Server
#520 - feature: generate Envoy configuration that exposes Prometheus metrics
#510 - feature: make port of Envoy Admin API available to Envoy config generators
#508 - feature: add option to run dataplane as a gateway without inbounds
#503 - feature: add
METRICS
column to the table output ofkumactl get meshes
to make it visible whether Prometheus settings have been configured
#502 - feature: automatically set default values for Prometheus settings in the Mesh resource
#501 - feature: add proto definitions for metrics that should be collected and exposed by dataplanes
#500 - chore: encapsulate proxy init into kuma-init container
#495 - feature: display CA type in kumactl get meshes
#494 - chore: update Envoy to v1.12.2
#493
Breaking changes:
- ⚠️ An
--dataplane-init-version
argument was removed. Init container was changed tokuma-init
which version is in sync with the rest of the Kuma containers.