AMQ Streams 1.1.0 on OpenShift Container Platform Release Notes

AMQ Streams now supports Kafka 2.1.1.

You must upgrade the Cluster Operator to 1.1.0 before you can upgrade to Kafka 2.1.1. For instructions, see AMQ Streams and Kafka upgrades.

Refer to the Kafka 2.1.0 and Kafka 2.1.1 Release Notes for additional information.

You can now configure AMQ Streams to use JBOD, a data storage configuration in which multiple disks or volumes are used. JBOD is one approach to providing increased data storage for Kafka brokers. It is not supported for Zookeeper.

See JBOD storage overview

Additional configuration options have been added for configuring resource metadata. You can add labels and annotations to control how Pods are treated by Istio or other services.

See Labels and Annotations

Use new template fields to customize your Pod creation:

See Customizing Pods

You can mount your own Secrets or ConfigMaps into a Kafka Connect deployment (including Kafka Connect S2I) by specifying the mount in your Pod deployment configuration as either:

This approach applies especially to confidential data, such as usernames, passwords, or certificates.

See Using external configuration and secrets

Define network policies for Kafka listeners. Use labels to describe permissible connections when configuring the listeners and the networkPolicyPeers field to specify the application pods or namespaces that will be allowed to access the Kafka cluster.

See Network policies

You can schedule certain rolling updates of your Kafka and Zookeeper clusters to start at a convenient time. Maintenance time windows allow you specify the days and times for planned maintenance using Cron expressions. Actions, such as certificate renewals, are started only during the maintenance window, though actions continue for as much time as required and do not stop when the window has ended.

See Maintenance time windows overview

You can configure the Cluster Operator to watch AMQ Streams custom resources across all OpenShift projects in your OpenShift cluster. When running in this mode, the Cluster Operator automatically manages clusters in any new projects or namespaces that are created.

See Deploying the Cluster Operator to watch all namespaces

You can customize the default image pull policy for containers in all pods deployed by the Cluster Operator. The image pull policy is configured using the environment variable STRIMZI_IMAGE_PULL_POLICY in the Cluster Operator deployment.

See Cluster Operator Configuration

It is now possible to configure the Pod Disruption Budgets created by default through the Cluster Operator template. The template is set by default for one Pod to be unavailable at a time, which can be can changed using the maxUnavailable field.

See Customizing Pod Disruption Budgets

Simple Authorization now supports Transactional IDs when specifying resource types.

See Simple Authorization

TLS sidecar, used to encrypt and decrypt all communication between the AMQ Streams components and Zookeeper, now supports the following configuration options:

See Healthcheck configurations

An external listener may be used to connect to a Kafka cluster outside an OpenShift environment.

AMQ Streams supports three types of external listeners:

With external listeners, you can:

See External listener

A new Annotations class holds a constant for the strimzi.io domain. Current uses of annotations have been refactored to use the new standardized class. Old annotations are deprecated, but still functional.