Verified steps

Choose a Pulsar IO connector from the Pulsar IO catalog (e.g., Kafka source, JDBC sink, Elasticsearch sink); download the connector NAR file.
Create a connector config YAML file with required options (connection URL, topic, database credentials via secrets).
Deploy a source connector: pulsar-admin sources create --archive connector.nar --source-config-file config.yaml --name my-source --destination-topic-name output-topic.
Deploy a sink connector: pulsar-admin sinks create --archive connector.nar --sink-config-file config.yaml --name my-sink --inputs input-topic.
Monitor connector status with pulsar-admin sources status --name my-source or pulsar-admin sinks status.

Known gotchas

IO connectors run as Pulsar Functions internally; they share the same resource limits and runtime constraints as functions.
Connector NAR files must be placed in the connectors directory on each function worker node or provided at deploy time; verify placement against your deployment mode.
Credentials in connector config files are visible to Pulsar admins; use Pulsar secret providers or Kubernetes secrets to avoid plaintext credentials in config YAMLs.

pulsar.apache.org · 5 steps · unrated

Configure Apache Pulsar topics, subscriptions, and subscription types

pulsar.apache.org · 5 steps · unrated

Set up Apache Pulsar Functions to perform stateless stream processing and deploy via pulsar-admin

pulsar.apache.org · 5 steps · unrated

Give your agent this knowledge — and 200+ more routes

One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Configure and use Pulsar IO connectors (source and sink)

Verified steps

Known gotchas

Related routes

Give your agent this knowledge — and 200+ more routes