- Kafka-on-Pulsar (KoP) KoP is a protocol handler to natively support the Apache Kafka protocol on Pulsar brokers. By adding the KoP protocol handler to your Pulsar cluster, you can migrate your existing Kafka applications and services to Pulsar without modifying the code.
- MQTT-on-Pulsar (MoP) MoP is a protocol handler to natively support the MQTT protocol on Pulsar brokers. By adding the MoP protocol handler to your Pulsar cluster, you can migrate your existing MQTT applications and services to Pulsar without modifying the code.
- AMQP-on-Pulsar (AoP) AoP is a protocol handler to natively support the AMQP protocol on Pulsar brokers. By adding the AoP protocol handler to your Pulsar cluster, you can migrate your existing AMQP applications and services to Pulsar without modifying the code.
Prerequisites
You have deployed a Pulsar cluster using the Pulsar Operators.Enable protocol handlers
- If you have deployed broker Pods on your Kubernetes cluster, the manifest will overwrite the existing configuration and recreate the broker Pods. You can customize other fields in the manifest as required.
- If you haven’t installed any components of Pulsar, you can create the
pulsar
namespace first and apply any of the following files to deploy brokers, BookKeeper, and ZooKeeper, with the related protocol handler enabled.
-
Apply a PulsarBroker custom resource manifest with
spec.config.protocolHandlers.<component>.enabled
set totrue
.- [1]
component
: represent the protocol handler (KoP, MoP, or AoP) to be enabled. Available options arekop
,aop
, andmop
. - [2]
enabled
: enable the protocol handler (KoP, MoP, or AoP). - [3]
proxyEnabled
: access the MoP or AoP protocol handler outside a Kubernetes cluster. The Pulsar proxy will forward your requests to the Pulsar broker. This property is only available for MoP and AoP.
- [1]
-
View the status of broker Pods.
You should see the following output: