Skip to content

Releases: nats-io/k8s

Release v0.13.1

15 Feb 19:20
7f5f903
Compare
Choose a tag to compare

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

07 Feb 22:35
36877af
Compare
Choose a tag to compare
v0.13.0

stan-0.13.0

08 Mar 20:25
36877af
Compare
Choose a tag to compare

A Helm chart for NATS Streaming

nats-kafka-0.13.0

13 Apr 17:08
36877af
Compare
Choose a tag to compare

A multi-connector bridge between NATS and Kafka.

nack-0.13.0

08 Mar 20:25
36877af
Compare
Choose a tag to compare

A Helm chart for NACK

Release v0.12.1

27 Jan 23:08
647073c
Compare
Choose a tag to compare

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 using helm upgrade
  • Added missing cipher_suites field to TLS config

Release v0.12.0

27 Jan 00:22
2b475a7
Compare
Choose a tag to compare

Changes for the nats chart:

Breaking

  • The podManagementPolicy value was introduced and set to Parallel by default, which controls the StatefulSet spec.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

25 Jan 03:24
6507760
Compare
Choose a tag to compare
v0.11.2

Release v0.11.0

11 Jan 00:12
eee54f9
Compare
Choose a tag to compare
v0.11.0

Release v0.10.0

02 Dec 22:01
Compare
Choose a tag to compare
v0.10.0