Main Changes since 0.15.0

• Add support for Kafka 2.4.0 and upgrade from Zookeeper 3.4.x to 3.5.x
• Drop support for Kafka 2.2.1 and 2.3.0
• Add KafkaConnector resource and connector operator
• Let user choose which node address will be used as advertised host (ExternalDNS, ExternalIP, InternalDNS, InternalIP or Hostname)
• Add support for tini
• When not explicitly configured by the user in jvmOptions, -Xmx option is calculated from memory requests rather than from memory limits
• Expose JMX port on Kafka brokers via an internal service
• Add support for externalTrafficPolicy and loadBalancerSourceRanges properties on loadbalancer and nodeport type services
• Add support for user quotas
• Add service discovery labels and annotations
• Add possibility to specify custom server certificates to TLS based listeners
• Add support for Istio protocol selection in service port names
  • Note: Strimzi is essentially adding a tcp- prefix to the port names in Kafka services and headless services. (e.g clientstls -> tcp-clientstls)

Full list of changes can be found under the 0.16.0 milestone.

Upgrading from Strimzi 0.15.x

See the documentation for upgrade instructions.

Main Changes since 0.14.0

• Drop support for Kafka 2.1.0, 2.1.1, and 2.2.0
• Add support for Kafka 2.3.1
• Improved Kafka rolling update
• Improved Kafka Exporter Grafana dashboard
• Add sizeLimit option to ephemeral storage (#1505)
• Add schedulerName to podTemplate (#2114)
• Allow overriding the auto-detected Kubernetes version
• Garbage Collection (GC) logging disabled by default
• Providing PKCS12 truststore and password in the cluster and clients CA certificates Secrets
• Providing PKCS12 keystore and password in the TLS based KafkaUser related Secret

Full list of changes can be found under the 0.15.0 milestone.

Upgrading from Strimzi 0.14.x

See the documentation for upgrade instructions.

Main Changes since 0.14.0

• Drop support for Kafka 2.1.0, 2.1.1, and 2.2.0
• Add support for Kafka 2.3.1
• Improved Kafka rolling update
• Improved Kafka Exporter Grafana dashboard
• Add sizeLimit option to ephemeral storage (#1505)
• Add schedulerName to podTemplate (#2114)
• Allow overriding the auto-detected Kubernetes version
• Garbage Collection (GC) logging disabled by default
• Providing PKCS12 truststore and password in the cluster and clients CA certificates Secrets
• Providing PKCS12 keystore and password in the TLS based KafkaUser related Secret

Full list of changes can be found under the 0.15.0 milestone.

Upgrading from Strimzi 0.14.x

See the documentation for upgrade instructions.

Main Changes

• Add support for configuring Ingress class
• Add support for setting custom environment variables in all containers
• Add liveness and readiness checks to Mirror Maker
• Allow configuring loadBalancerIP for LoadBalancer type services
• Allow setting labels and annotations for Persistent Volume Claims
• Add support for Jaeger tracing in Kafka Mirror Maker and Kafka Connect
• Add support for deploying Kafka Exporter
• Add initial support for OAuth authentication

Full list of changes can be found under the 0.14.0 milestone.

Upgrading from Strimzi 0.13.x

See the documentation for upgrade instructions.

Main Changes since 0.14.0-rc2

• Updated dependencies due to CVEs (jackson-databind library)
• Properly passing JWKS refresh and expiration intervals in OAuth configuration
• Respecting the HTTP port configuration in Strimzi bridge
• Using the right default container images for TLS sidecars
• Other improvements to Maven build, Docs and system tests

Full list of changes can be found under the 0.14.0 milestone.

Upgrading from Strimzi 0.13.x

See the documentation for upgrade instructions.

Main Changes since 0.14.0-rc1

• Manage network policies between Kafka Exporter and Kafka brokers.
• Documentation improvements
• CI improvements
• System test improvements

Full list of changes can be found under the 0.14.0 milestone.

Upgrading from Strimzi 0.13.x

See the documentation for upgrade instructions.

Main Changes

• Add support for configuring Ingress class (#1716)
• Add support for setting custom environment variables in all containers
• Add liveness and readiness checks to Mirror Maker
• Allow configuring loadBalancerIP for LoadBalancer type services
• Allow setting labels and annotations for Persistent Volume Claims
• Add support for Jaeger tracing in Kafka Mirror Maker and Kafka Connect
• Add support for deploying Kafka Exporter
• Add initial support for OAuth authentication

Full list of changes can be found under the 0.14.0 milestone.

Upgrading from Strimzi 0.13.x

See the documentation for upgrade instructions.

Main Changes

• Allow users to manually configure ACL rules (for example, using kafka-acls.sh) for special Kafka users * and ANONYMOUS without them being deleted by the User Operator
• Add support for configuring a Priority Class name for Pods deployed by Strimzi
• Add support for Kafka 2.3.0
• Add support for Kafka User resource status
• Add support for Kafka Connect resource status
• Add support for Kafka Connect S2I resource status
• Add support for Kafka Bridge resource status
• Add support for Kafka Mirror Maker resource status
• Add support for DNS annotations to nodeport type external listeners

Full list of changes can be found under the 0.13.0 milestone.

Upgrading from Strimzi 0.12.x

See the documentation for upgrade instructions.

Main Changes

• Allow users to manually configure ACL rules (for example, using kafka-acls.sh) for special Kafka users * and ANONYMOUS without them being deleted by the User Operator
• Add support for configuring a Priority Class name for Pods deployed by Strimzi
• Add support for Kafka 2.3.0
• Add support for Kafka User resource status
• Add support for Kafka Connect resource status
• Add support for Kafka Connect S2I resource status
• Add support for Kafka Bridge resource status
• Add support for Kafka Mirror Maker resource status
• Add support for DNS annotations to nodeport type external listeners

Full list of changes can be found under the 0.13.0 milestone.

Upgrading from Strimzi 0.12.x

See the documentation for upgrade instructions.

Changes since 0.12.1:

• Fix deprecated Topic Operator to work with new images #1765
• Fix null check in EU/UO role binding management #1766
• Fix plugin isolation in Kafka Connect S2I #1805
• Fix validation of invalid Kafka versions #1727

Changes since 0.12.0:

• Fix a bug in the maintenance window used for certificate operations #1728

0.12.0

• Drop support for Kubernetes 1.9 and 1.10 and OpenShift 3.9 and 3.10.
  Versions supported since Strimzi 0.12.0 are Kubernetes 1.11 and higher and OpenShift 3.11 and higher.
  This was required because the CRD versioning and CRD subresources support.
• Added support for Kafka 2.2.1 and 2.1.1, dropped support for Kafka 2.0.0 and 2.0.1
• Persistent storage improvements
  • Add resizing of persistent volumes
  • Allow to specify different storage class for every broker
  • Adding and removing volumes in Jbod Storage
• Custom Resources improvements
  • New CRD version v1beta1. See documentation for more information about upgrading from v1alpha1 to v1beta1.
  • Log at the warn level when a custom resource uses deprecated or unknown properties
  • Add initial support for the status sub-resource in the Kafka custom resource
• Add support for Strimzi Kafka Bridge for HTTP protocol
• Reduce the number of container images needed to run Strimzi to just two: kafka and operator.
• Add support for unprivileged users to install the operator with Helm
• Support experimental off-cluster access using Kubernetes Nginx Ingress
• Add ability to configure Image Pull Secrets for all pods in Cluster Operator
• Support for SASL PLAIN mechanism in Kafka Connect and Mirror Maker (for use with non-Strimzi Kafka cluster)

Upgrading from Strimzi 0.11.0

• Backup the existing Cluster Operator resources
• Update the Cluster Operator. You will need to modify the installation files according to the namespace the Cluster Operator is running in. For more information, see Strimzi documentation.
• If you modified one or more environment variables in your existing Cluster Operator Deployment, edit
  install/cluster-operator/050-Deployment-cluster-operator.yaml to reflect the changes that you made.
• When you have an updated configuration you can deploy it along with the rest of the install resources:

kubectl apply -f install/cluster-operator

• Wait for the associated rolling updates to complete.
• Update existing resources to the v1beta1 API version and to cope with deprecated custom resource properties. For more information, see Strimzi documentation.

Changes since 0.12.0-rc1

• Throw error when a TLS KafkaUser with name >64 chars is created (#1698)
• Workaround the versioning issues in CRDs with KafkaStatus after version upgrade (#1695)
• Fix problems with certificate renewals caused by an incorrect commit (#1688)
• Update RBAC resources from v1beta1 to v1

Upgrading from Strimzi 0.11.x

See the documentation - chapter 8. Strimzi and Kafka upgrades. Also notice the section 9. Strimzi resource upgrades about upgrading the resources from v1alpha1 to v1beta1.

Main Changes

• Drop support for Kubernetes 1.9 and 1.10 and OpenShift 3.9 and 3.10. Versions supported since Strimzi 0.12.0 are Kubernetes 1.11 and higher and OpenShift 3.11 and higher. This was required because the CRD versioning and CRD sub-resources support.
• Added support for Kafka 2.2.0 and 2.1.1, dropped support for Kafka 2.0.0 and 2.0.1
• Persistent storage improvements
  • Add resizing of persistent volumes
  • Allow to specify different storage class for every broker
  • Adding and removing volumes in Jbod Storage
• Custom Resources improvements
  • New CRD version v1beta1. See documentation for more information about upgrading from v1alpha1 to v1beta1.
  • Log at the warn level when a custom resource uses deprecated or unknown properties
  • Add initial support for the status sub-resource in the Kafka custom resource
• Add support for Strimzi Kafka Bridge for HTTP protocol
• Reduce the number of container images needed to run Strimzi to just two: kafka and operator.
• Add support for unprivileged users to install the operator with Helm
• Support experimental off-cluster access using Kubernetes Nginx Ingress
• Add ability to configure Image Pull Secrets for all pods in Cluster Operator
• Support for SASL PLAIN mechanism in Kafka Connect and Mirror Maker (for use with non-Strimzi Kafka cluster)

Full list of changes can be found under the 0.12.0 milestone.

Upgrading from Strimzi 0.11.x

See the documentation - chapter 8. Strimzi and Kafka upgrades. Also notice the section 9. Strimzi resource upgrades about upgrading the resources from v1alpha1 to v1beta1.

Changes since 0.11.3:

• Fix network policies on OpenShift 3.11 (#1606)
• Add yum update to our Dockerfiles (#1628)

Changes since 0.11.2:

• Resources configuration should be properly passed from MirrorMaker CR to the Deployment (#1494)
• Fix JMV options for Kafka Mirror Maker (#1570)
• Do not touch the secrets with CA which were created by the users (#1497)
• Support for SASL PLAIN authentication in Kafka Connect and Kafka Connect S2I (#1584)

Changes since 0.11.1:

• Fix NPE which breaks reconciliation when overrides are used without NodePorts (#1456)

Assorted bug-fixes:

• OpenShift detection on OpenShfit 4.0 (#1405)
• Zookeeper leader selection during certificate renewal (#1404)
• Fix network policies between CO and Zookeeper (#1402)
• Fix several NPE exceptions (#1399, #1386)
• Fix RBAC issue when User Operator is listening to different namespace (#1391)
• Fix problem with upgrade form 0.8.x (#1397)
• Fix regular rolling updates outside of maintenance windows (#1398)

Minor improvements:

• Improve log message for unsupported Kafka versions (#1394)

Main changes:

• Add support for JBOD storage for Kafka brokers
• Allow users to configure the default ImagePullPolicy
• Sample Prometheus alerts
• More configuration options for off cluster access
  • Configure advertised hosts and ports
  • Configure NodePort numbers
  • Configure hosts OpenShift routes
  • Add additional DNS name for bootstrap service
• Support for watching all namespaces
• Operator Lifecycle Manager integration

Full list of changes can be found under the 0.11.0 milestone.

Upgrading from Strimzi 0.10.0

• Backup the existing Cluster Operator resources
• Update the Cluster Operator. You will need to modify the installation files according to the namespace the Cluster Operator is running in. For more information, see strimzi documentation.
• If you modified one or more environment variables in your existing Cluster Operator Deployment, edit
  install/cluster-operator/050-Deployment-cluster-operator.yaml to reflect the changes that you made.
• When you have an updated configuration you can deploy it along with the rest of the install resources:

kubectl apply -f install/cluster-operator

• Wait for the associated rolling updates to complete.
• Update existing resources to cope with deprecated custom resource properties.
  • If you have Kafka resources that specify Kafka.spec.topicOperator, rewrite them to use Kafka.spec.entityOperator.topicOperator instead.

Changes since RC1

• Fixes to YAML files
• Documentation updates
• Minor improvements to watching of all namespaces

Upgrading from Strimzi 0.10.0

• Backup the existing Cluster Operator resources
• Update the Cluster Operator. You will need to modify the installation files according to the namespace the Cluster Operator is running in. For more information, see strimzi documentation.
• If you modified one or more environment variables in your existing Cluster Operator Deployment, edit
  install/cluster-operator/050-Deployment-cluster-operator.yaml to reflect the changes that you made.
• When you have an updated configuration you can deploy it along with the rest of the install resources:

kubectl apply -f install/cluster-operator

• Wait for the associated rolling updates to complete.
• Update existing resources to cope with deprecated custom resource properties.
  • If you have Kafka resources that specify Kafka.spec.topicOperator, rewrite them to use Kafka.spec.entityOperator.topicOperator instead.