Download Kuma 0.2.0 and run it now:
CHANGELOG:
- Fix an issue with
Access Log Server
(integrated intokuma-dp
) on Kubernetes
by replacingGoogle gRPC client
withEnvoy gRPC client
#306 - Settings of a
kuma-sidecar
container, such asReadinessProbe
,LivenessProbe
andResources
,
are now configurable
#304 - Added support for
TCP
logging backends, such asELK
andSplunk
#300 Builtin CA
onKubernetes
is now (re-)generated by aController
#299- Default
Mesh
onKubernetes
is now (re-)generated by aController
#298 - Added
Kubernetes Admission WebHook
to apply defaults toMesh
resources
#297 - Upgraded version of
kubernetes-sigs/controller-runtime
dependency
#293 - Added a concept of
RuntimePlugin
tokuma-cp
#296 - Updated
LDS
to configureaccess_loggers
onoutbound
listeners
according toTrafficLog
resources
#276 - Changed default locations where
kuma-dp
is looking forenvoy
binary
#268 - Added model for
TrafficLog
resource withFile
as a logging backend
#266 - Added
kumactl install database-schema
command to generate DB schema
used bykuma-cp
onuniversal
environment
#236 - Automated release of
Docker
images
#265 - Changed default location where auto-generated Envoy bootstrap configuration is saved to
#261 - Added support for multiple
kuma-dp
instances on a single Linux machine
#260 - Automated release of
*.tar
artifacts
#250