Releases: nats-io/k8s
Releases · nats-io/k8s
Release v0.13.1
Added support for nats.tls.allowNonTLS
for mixed TLS and non-TLS mode:
nats:
client:
port: 4222
tls:
allowNonTLS: true
secret:
name: nats-server-tls
ca: "ca.crt"
cert: "tls.crt"
key: "tls.key"
timeout: "5s"
Release v0.13.0
v0.13.0
stan-0.13.0
A Helm chart for NATS Streaming
nats-kafka-0.13.0
A multi-connector bridge between NATS and Kafka.
nack-0.13.0
A Helm chart for NACK
Release v0.12.1
Changes:
- Default liveness check for nats helm chart bumped to 60s to mitigate terminationGracePeriodSeconds and lame duck / graceful exit causing an empty container to hang
- Added
upgrade
parameter to allow explicitly marking an upgrade as an alternative of usinghelm upgrade
- Added missing cipher_suites field to TLS config
Release v0.12.0
Changes for the nats chart:
Breaking
- The
podManagementPolicy
value was introduced and set toParallel
by default, which controls the StatefulSetspec.podManagementPolicy
field. This field is immutable and cannot be changed on an existing StatefulSet; to upgrade from an older chart version, add the value:podManagementPolicy: OrderedReady
Improvements
- Introduces using /healthz as a startup check when the image version is 2.7.1 during upgrades
- The preStop command no longer waits for
terminationGracePeriodSeconds
since this blocks pod termination, this workaround used to exist for when nats-server did not handle TERM but since v2.2 it does now so lame duck should work correctly without being stopped prematurely. - podManagementPolicy is now set to
Parallel
by default . - readiness probe is disabled now by default (it was the same as livenessProbe and the startupProbe covers the same check during startup now)
In case have to disable the startup check, then can do the following:
nats:
healthcheck:
startup:
enabled: false
Release v0.11.2
v0.11.2
Release v0.11.0
v0.11.0
Release v0.10.0
v0.10.0