AMQ Streams 1.1.0 on OpenShift Container Platform Release Notes
Release Notes for AMQ Streams 1.1.0
Chapter 1. Features
The features added in this release, and that were not in previous releases of the AMQ Streams, are outlined below.
- Kafka 2.1.1 support
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.Note
Kafka 2.0.0 is supported only for upgrade purposes.
- JBOD storage option
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.
- Labels and annotations for resources
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.
- New Pod template fields
Use new template fields to customize your Pod creation:
terminationGracePeriodSecondsdefines the period of time, in seconds, by which a Pod must have terminated gracefully.
imagePullSecretsdefines a list of references to OpenShift Secrets that can be used for pulling container images from private repositories.
securityContextsets pod-level security attributes for containers running as part of a given Pod.
See Customizing Pods
- Mounting Secrets for Kafka Connect
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:
- Environment variables
- Volumes (using property files referenced in the configuration)
This approach applies especially to confidential data, such as usernames, passwords, or certificates.
- Network policies
Define network policies for Kafka listeners. Use labels to describe permissible connections when configuring the listeners and the
networkPolicyPeersfield to specify the application pods or namespaces that will be allowed to access the Kafka cluster.
See Network policies
- Maintenance time window
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.
- Watch resources across all namespaces
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.
- Custom ImagePullPolicy
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_POLICYin the Cluster Operator deployment.
- Pod Disruption Budgets
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
Chapter 2. Enhancements
The following table lists the enhancements in AMQ Streams 1.1.0.
- User authorization
Simple Authorization now supports Transactional IDs when specifying resource types.
- TLS sidecar health checks
TLS sidecar, used to encrypt and decrypt all communication between the AMQ Streams components and Zookeeper, now supports the following configuration options:
readinessProbedefines when a container can start accepting traffic
livenessProbedefines when to restart a container
- Enriched configuration options for off-cluster access
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:
- Override host names and ports
- Add DNS names for the bootstrap service
- Specify target OpenShift routes
- Configure NodePort numbers
- Sample Prometheus alerts
- Example Prometheus alerting rules are provided for Kafka and Zookeeper metrics. The examples may be used when configuring Prometheus Alertmanager.
- Annotations refactoring
Annotationsclass holds a constant for the
strimzi.iodomain. Current uses of annotations have been refactored to use the new standardized class. Old annotations are deprecated, but still functional.
- Kafka and Zookeeper shutdown handling
- TLS sidecar now shuts down after the main pods so that connections to Zookeeper are maintained for a clean shutdown.
- Certificate validity
Changes to the number of days a security certificate should be valid through
renewalDaysare now propagated to
UserOperatorto override the (365 day) default validity.
Chapter 3. Fixed issues
The following table lists the issues fixed in AMQ Streams 1.1.0.
Chapter 4. Known issues
There are no known issues for AMQ Streams 1.1.0.