Use a Remote Connector with Pulsar Proxy

  1. Download connector-plugin-standalone.jar.

  2. Enable pulsar proxy by modifying custom_values.yaml during Fusion installation as below:

    pulsar:
      components:
        proxy: true
  3. Perform kubectl get svc and get the load balancer IP of Pulsar proxy.

    Example:

    NAME                              TYPE           CLUSTER-IP     EXTERNAL-IP      PORT(S)                               AGE
    <namespace>-pulsar-pulsar-proxy   LoadBalancer   10.75.1.81     34.105.102.171   80:32182/TCP,6650:31884/TCP           6m7s
  4. Use load balancer ip for pulsar.service-url and pulsar.admin-url in config.yaml as shown below and execute following command.

    java -jar connector-plugin-standalone.jar config.yaml

Example config.yaml

pulsar:
  service-url: pulsar+ssl://35.230.38.171:6651
  #service-url: pulsar://35.230.38.171:6651 non-ssl
  admin-url: https://35.230.38.171:443
  tenant-name: ppt
  authenticationEnabled: true
  tlsEnabled: true
  tlsTrustCertsFilePath: ca.crt

proxy:
  user: test
  password: test
  url: https://fusiontest.com/

plugin:
  path: fs.zip
  type:
    suffix: remote

Description of Pulsar proxy properties

Property Description

pulsar.service-url

Pulsar Service URL. e.g. pulsar://35.247.112.3:6650, pulsar+ssl://35.230.38.171:6651

pulsar.admin-url

Pulsar Admin URL. e.g. http://35.247.112.3:8080, https://35.247.112.3:443

tenant-name

Pulsar Tenant Name (kube namespace)

authenticationEnabled

Pulsar authentication enabled flag

tlsEnabled

TLS enabled flag

tlsTrustCertsFilePath

Trust certs file path

proxy.user

Fusion proxy user

proxy.password

Fusion proxy password

proxy.url

Fusion proxy url

plugin.path

Path of plugin zip file

plugin.type.suffix

Plugin type suffix. e.g 'lucidworks.testplugin' id with suffix 'remote' will be 'lucidworks.testplugin.remote' and name 'Test Connector' will be 'Test Connector (remote)'