Red Hat AMQ Streams is Red Hat's enterprise distribution of Apache Kafka for Kubernetes and OpenShift. It is built on the open-source Strimzi project, which runs Kafka as a set of Kubernetes operators, and adds Red Hat's enterprise support, certification, and integration with the OpenShift platform. It targets organizations standardized on OpenShift that want supported Kafka managed the Kubernetes-native way.

Kafka as Kubernetes operators

The Strimzi foundation models Kafka entirely through Kubernetes custom resources. You declare a cluster, topics, and users as YAML objects, and operators reconcile them - provisioning brokers, handling rolling upgrades, managing certificates, and recovering failed pods. A Kafka cluster becomes declarative infrastructure managed like any other Kubernetes workload, with GitOps-friendly configuration.

apiVersion: kafka.strimzi.io/v1beta2
kind: KafkaTopic
metadata:
  name: events
  labels:
    strimzi.io/cluster: my-cluster
spec:
  partitions: 12
  replicas: 3
  config:
    retention.ms: 604800000

What Red Hat adds over Strimzi

  • Enterprise support and lifecycle - certified builds, security patches, and long-term support SLAs.
  • OpenShift integration - operators in the OperatorHub, console integration, and alignment with OpenShift security and networking.
  • Part of the AMQ family - alongside AMQ Broker (ActiveMQ-based messaging) for teams needing both streaming and classic messaging under one vendor.

Where it fits

  • Enterprises running OpenShift that want supported, Kubernetes-native Kafka.
  • Hybrid/on-prem deployments where a cloud-vendor Kafka service isn't an option.
  • GitOps shops that want Kafka topics and clusters declared as version-controlled resources.

How to choose

AMQ Streams makes sense when OpenShift is your platform and you want Red Hat support; the underlying Strimzi is the same technology if you prefer pure open source on plain Kubernetes without a support contract. Against managed cloud Kafka (MSK, Confluent Cloud), AMQ Streams keeps you in control of the cluster on your own Kubernetes - more operational responsibility, but full portability across on-prem and any cloud, and no dependence on a single cloud provider's service.