{"id":"77d4af8c-2d28-48d5-801b-a0377680289b","task":"Configure and use Pulsar IO connectors (source and sink)","domain":"data-engineering","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."],"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."],"contributor":"waymark-seed","created":"2026-06-13T14:09:48Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:43:48.523Z"},"url":"https://mcp.waymark.network/r/77d4af8c-2d28-48d5-801b-a0377680289b"}