AMQ Streams 1.2 on OpenShift Container Platform Release Notes

AMQ Streams now supports Kafka 2.2.1.

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

After you have performed an upgrade, custom resources that use kafka.strimzi.io/v1alpha1 must be updated as the API version is deprecated.

Refer to the Kafka 2.2.0 and Kafka 2.2.1 Release Notes for additional information.

As a requirement for the new features, AMQ Streams now supports OpenShift Container Platform 3.11 and 4.x.

OpenShift Container Platform 3.9 and 3.10 is no longer supported.

AMQ Streams can be installed on OpenShift 4.x:

The YAML files describing the CRDs provided with AMQ Streams now support multiple versions. The change means that there is now support for a schema specific to an API version.

See Custom resources

It is now possible to add or remove volumes from JBOD storage to respond to new requirements for storing data. To make the change, the volumes spec for the Kafka resource is edited and updated. Following the update, new topics can be assigned to the disks or existing partitions can be reassigned.

See Removing volumes from JBOD storage

To respond to an increased demand for storage, you can now increase the size of the persistent volumes used for the storage of messages and logs in an existing AMQ Streams cluster.

A persistent volume can be resized if:

Persistent volume size is defined in the size field in the spec.kafka.storage and spec.zookeeper.storage properties:

apiVersion: kafka.strimzi.io/v1beta1
kind: Kafka
metadata:
  name: my-cluster
spec:
  kafka:
    # ...
    storage:
      type: persistent-claim
      size: 2000Gi
      class: my-storage-class
    # ...
  zookeeper:
    # ...

apiVersion: kafka.strimzi.io/v1beta1
kind: Kafka
metadata:
  name: my-cluster
spec:
  kafka:
    # ...
    storage:
      type: persistent-claim
      size: 2000Gi
      class: my-storage-class
    # ...
  zookeeper:
    # ...

See Resizing persistent volumes

This release includes the following changes to the management of container images for AMQ Streams on OpenShift.

The AMQ Streams Kafka Bridge provides a RESTful interface to AMQ Streams, offering the advantages of a web API that is easy to use and connect with AMQ Streams without the need to interpret the Kafka protocol.

The HTTP Bridge supports HTTP producer and consumer requests to:

The methods provide JSON responses and HTTP response code error handling.

See Using the AMQ Streams Kafka Bridge

The new status property for a AMQ Streams-specific custom resource publishes the current state of the resource to users and tools that need the information.

See AMQ Streams custom resource status

API version v1alpha1 has been deprecated for this release of AMQ Streams.

Custom resources that use kafka.strimzi.io/v1alpha1 must be updated to use kafka.strimzi.io/v1beta1.

See AMQ Streams resource upgrades