All DSP releases prior to DSP 1.4.0 use Gravity, a Kubernetes orchestrator, which has been announced end-of-life. We have replaced Gravity with an alternative component in DSP 1.4.0. Therefore, we will no longer provide support for versions of DSP prior to DSP 1.4.0 after July 1, 2023. We advise all of our customers to upgrade to DSP 1.4.0 in order to continue to receive full product support from Splunk.
Configure Pulsar to expose with loadbalancer
In a 1.4.x processing cluster, DSP uses the open-source Pulsar bundle. If you want to configure a topic and use it for ingesting data on the processing cluster, follow the steps below.
- Enable the proxy.
dsp config set pulsar proxy_enabled=true
- Deploy your changes.
dsp deploy pulsar
- Validate changes
kubectl get pods -n pulsar <Kubectl get svc -n pulsar
- Change the service type to a loadbalancer.
kubectl patch svc pulsar-proxy -n pulsar -p '{"spec": {"type": "LoadBalancer"}}'
- Patch the node IP as a loadbalancer IP if you do not have a public IP enabled for the cluster.
curl ifconfig.me kubectl patch svc pulsar-proxy -n pulsar -p '{"spec": {"type": "LoadBalancer", "externalIPs":["<IP>"]}}'
- Create a topic.
./pulsar-admin topics create-partitioned-topic persistent://public/default/direct-partitionedmay23 -p 2 ./pulsar-admin topics list public/default | wc -l ./pulsar-admin namespaces set-retention public/default -s -1 -t 1h
- Generate and retrieve your certificate.
kubectl get secret -n pulsar pulsar-tls-broker -o json | jq -r '.data."tls.crt"' | base64 --decode > my-cert.pem kubectl get secret -n pulsar pulsar-tls-broker -o json | jq -r '.data."tls.key"' | base64 --decode > my-key.pem kubectl get secret -n pulsar pulsar-tls-broker -o json | jq -r '.data."ca.crt"' | base64 --decode > ca-cert.cert
- Create an Apache Pulsar connection in your DSP cluster. See Create a DSP connection to Apache Pulsar for more information.
- Create a pipeline and begin ingesting data.
Create a DSP connection to Apache Pulsar | Connecting Google Cloud Pub/Sub to your DSP pipeline |
This documentation applies to the following versions of Splunk® Data Stream Processor: 1.4.2, 1.4.3, 1.4.4, 1.4.5
Feedback submitted, thanks!