Pre-installation steps

Before installing the probe, you must perform the following tasks:

  1. Securing communications with the Pulsar Broker
  2. Securing communications with the ObjectServer
  3. (Optional) Creating a persistent volume claim to provide probe configuration

Securing communications with the Pulsar Broker

To secure Probe and Pulsar Broker communication, you must pre-create a secret to store the required certificates before installing the probe. The example below creates a kubernetes secret contains the trusted TLS certificate, client certificates and authentication plugin class name in your pre-created namespace.

kubernetes create secret generic message-bus-pulsar-cert --namespace <NAMESPACE> \
  --from-file=tlsTrustCertFile=certs/ca.cert.pem \
  --from-file=tlsCertFile=certs/admin.cert.pem \
  --from-file=tlsKeyFile=certs/admin.key-pk8.pem \
  --from-literal=authPluginClassName=org.apache.pulsar.client.impl.auth.AuthenticationTls

Securing communications with the ObjectServer

See Secure probe and ObjectServer communication requirements.

(Optional) Creating a persistent volume claim to provide probe configuration

To allow the probe to access the custom probe files in Persistent Volume (PV), you must pre-create a Persistent Volume Claim (PVC) . The PVC must have access mode of ReadWriteMany (RWX). You must determine the amount of storage available to the PVC according to your total size of files that you want to store in PV.