0.19.0-rc1

Main Changes since 0.18.0

• Add support for authorization using Open Policy Agent
• Add support for scale subresource to make scaling of following resources easier:
  • KafkaConnect
  • KafkaConnectS2I
  • KafkaBridge
  • KafkaMirrorMaker
  • KafkaMirrorMaker2
  • KafkaConnector
• Remove deprecated Kafka.spec.topicOperator classes and deployment logic
• Use Java 11 as the Java runtime
• Removed the need to manually create Cruise Control metrics topics if topic auto creation is disabled.
• Migration to Helm 3
• Refactored the format of the KafkaRebalance resource's status. The state of the rebalance is now displayed in the associated Condition's type field rather than the status field. This was done so that the information would display correctly in various Kubernetes tools.
• Added performance tuning options to the KafkaRebalance CR and the ability to define a regular expression that will exclude matching topics from a rebalance optimization proposal.
• Use Strimzi Kafka Bridge 0.18.0
• Make it possible to configure labels and annotations for secrets created by the User Operator
• Strimzi Kafka Bridge metrics integration:
  • enable/disable metrics in the KafkaBridge custom resource
  • new Grafana dashboard for the bridge metrics
• Support dynamically changeable logging in the Entity Operator and Kafka Bridge

Deprecations and removals

Deprecation of Helm v2 chart

The Helm v2 support will end soon.
Bug fixing should stop on August 13th 2020 and security fixes on November 13th.
See https://helm.sh/blog/covid-19-extending-helm-v2-bug-fixes/ for more details.

In sync with that, the Helm v2 chart of Strimzi Cluster Operator is now deprecated and will be removed in the future as Helm v2 support ends.
Since Strimzi 0.19.0, we have a new chart for Helm v3 which can be used instead.

Removal of v1alpha1 versions of several custom resources

In Strimzi 0.12.0, the v1alpha1 versions of the following resources have been deprecated and replaced by v1beta1:

• Kafka
• KafkaConnect
• KafkaConnectS2I
• KafkaMirrorMaker
• KafkaTopic
• KafkaUser

In the next release, the v1alpha1 versions of these resources will be removed.
Please follow the guide for upgrading the resources: https://strimzi.io/docs/operators/latest/deploying.html#assembly-upgrade-str.

Removal deprecated cadvisor metric labels

The pod_name and container_name labels provided on the cadvisor metrics are now just pod and container starting from Kubernetes 1.16.
We removed the old ones from the Prometheus scraping configuration/alerts and on the Kafka and ZooKeeper dashboard as well.
It means that the charts related to memory and CPU usage are not going to work on Kuvbernetes version previous 1.14.
For more information on what is changed: #3312

Deprecation of monitoring port on Kafka and ZooKeeper related services

The PodMonitor resource is now used instead of the ServiceMonitor for scraping metrics from Kafka, ZooKeeper, Kafka Connect and so on.
For this reason, we are deprecating the monitoring port tcp-prometheus (9404) on all the services where it is declared (Kafka bootstrap, ZooKeeper client and so on).
This port will be removed in the next release.
Together with it we will also remove the Prometheus annotation from the service.

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

Upgrading from Strimzi 0.18.0

See the documentation for upgrade instructions.

0.18.0

Main Changes since 0.17.0

• Add possibility to set Java System Properties via custom resources
• Make it possible to configure PodManagementPolicy for StatefulSets
• Update build system to use yq version 3 (https://github.com/mikefarah/yq)
• Add more metrics to Cluster, User and Topic Operators
• New Grafana dashboard for Operator monitoring
• Allow ssl.cipher.suites, ssl.protocol and ssl.enabled.protocols to be configurable for Kafka and the different components supported by Strimzi
• Add support for user configurable SecurityContext for each Strimzi container
• Add support for Kafka 2.4.1 and 2.5.0
• Remove TLS sidecars from ZooKeeper pods, using native ZooKeeper TLS support instead
• Use Strimzi Kafka Bridge 0.16.0 with support for CORS in the HTTP protocol
• Pass HTTP Proxy configuration from operator to operands
• Add Cruise Control support

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

Upgrading from Strimzi 0.17.0

See the documentation for upgrade instructions.

0.18.0-rc2

Main Changes since 0.18.0-rc1

• Improve the KafkaRebalance resources
• Add the KafkaRebalance resource to the strimzi category
• Add KafkaRebalance resources to Operators Grafana dashboard
• Make sure TLS protocol can be configured in Kafka brokers
• Fix Prometheus installation guide

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

Upgrading from Strimzi 0.17.0

See the documentation for upgrade instructions.

0.18.0-rc1

Main Changes since 0.17.0

• Add possibility to set Java System Properties via custom resources
• Make it possible to configure PodManagementPolicy for StatefulSets
• Update build system to use yq version 3 (https://github.com/mikefarah/yq)
• Add more metrics to Cluster, User and Topic Operators
• New Grafana dashboard for Operator monitoring
• Allow ssl.cipher.suites, ssl.protocol and ssl.enabled.protocols to be configurable for Kafka and the different components supported by Strimzi
• Add support for user configurable SecurityContext for each Strimzi container
• Add support for Kafka 2.4.1 and 2.5.0
• Remove TLS sidecars from ZooKeeper pods, using native ZooKeeper TLS support instead
• Use Strimzi Kafka Bridge 0.16.0 with support for CORS in the HTTP protocol
• Pass HTTP Proxy configuration from operator to operands
• Add Cruise Control support

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

Upgrading from Strimzi 0.17.0

See the documentation for upgrade instructions.

0.17.0

Main Changes since 0.16.x

• Add possibility to set Java System Properties via CR yaml
• Add support for Mirror Maker 2.0
• Add Jmxtrans deployment
• Add public keys of TLS listeners to the status section of the Kafka CR
• Various bug-fixes
• Dependency upgrades to avoid CVEs
• Improved system tests and documentation

Note: The Connector operator is now using network policies to make sure it has access to Kafka Connect even when network policies deny all traffic. If you want to use the Connector operator while also using the REST API directly, you should create additional network policies to give access to the REST API to your applications as well.

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

Upgrading from Strimzi 0.16.x

See the documentation for upgrade instructions.

0.17.0-rc4

Main Changes since 0.17.0-rc3

• Make sure the ZookeeperScaler does work will with custom CAs without the PKCS12 files

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

Upgrading from Strimzi 0.16.x

See the documentation for upgrade instructions.

0.17.0-rc3

Main Changes since 0.17.0-rc2

• Fixed NPE which happen in KafkaRoller under rare circumstances
• Fix ordering of addresses in config map to avoid random rolling updates
• Fix scaling of Zookeeper 3.5
• Fix several issues with Connector operator and Mirror Maker 2
• Many other bugs, test and docs improvements

Note: The Connector operator is now using network policies to make sure it has access to Kafka Connect even when network policies deny all traffic. If you want to use the Connector operator while also using the REST API directly, you should create additional network policies to give access to the REST API to your applications as well.

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

Upgrading from Strimzi 0.16.x

See the documentation for upgrade instructions.

0.17.0-rc2

Main Changes since 0.17.0-rc1

• Support for pausing / resuming MM2 connectors
• Fix bug in Kafka rack awareness configuration
• Add network policies for Kafka connect when using the connector operator
• Fix rolling update restart when configuration changes
• Fix ZooKeeper scale-up bug
• Validate the replication factor in relation to number of Kafka replicas
• Various bug-fixes
• Dependency upgrades to avoid CVEs
• Improved system tests and documentation

Note: The Connector operator is now using network policies to make sure it has access to Kafka Connect even when network policies deny all traffic. If you want to use the Connector operator while also using the REST API directly, you should create additional network policies to give access to the REST API to your applications as well.

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

Upgrading from Strimzi 0.16.x

See the documentation for upgrade instructions.

0.17.0-rc1

Main Changes since 0.16.0

• Add possibility to set Java System Properties via CR yaml
• Add support for Mirror Maker 2.0
• Add Jmxtrans deployment
• Add public keys of TLS listeners to the status section of the Kafka CR

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

Upgrading from Strimzi 0.16.x

See the documentation for upgrade instructions.

0.16.2

Main Changes since 0.16.1

• Fix bug in upgrade when the Kafka.spec.kafka.version field is not specified
• Fix network policies for port 9091 on older Kubernetes versions