Before breaking changes

The next release will change container arguments along with properties files' paths, and rename the broker service to kafka. Upgrades beyond this release might be messy.

Accepts an additional client per zookeeper pod

In scale=1 scenarios (or whenever the number of zookeeper pods is equal to the number of kafka pods) zookeeper must allow additional clients, for example to run some admin commands. See 0515747.

Kafka 2.2.1

This release bumps Kafka to the latest build, on the same Oracle JRE as before (see #263).

Also it includes a variant scale-3-5-nopzoo that has only one Zookeeper statefulset (#277).

Furthermore, anyone using Prometheus Operator might want to take a look at 50345f2.

Restores apply -f behavior

Now the introduction of Kustomize support is backwards compatible, bar the change of default storage class name (#270).

Kustomization support, "standard" storage class

Adds several examples for kubectl apply -k.

Note: the default storage class name has changed through #270. The old names are found in the gke-regional variant.

Kafka 2.1.1 and Cruise Control

See #248, Cruise Control #218, Cruise Control UI solsson/dockerfiles#22

Critical Zookeeper persistence bugfix

See the upgrade suggestions in #228 (comment) and #228 (comment).

If anyone lost zookeeper state it should be possible to recover from snapshot files. We haven't tested that though.

All five zookeeper pods reachable again

See #231.

Evaluate Zookeeper client connection limits

Things like #230 can be introduced now when we've destabilized.

Fix topic metadata gone after Zookeeper downtime

Critical bugfix release for #89, see upgrade path in #228 and #227.