Deploy Pulse Add-on Services
You can deploy Pulse Add-on services by sending an API request to the Pulse Manager Server. These services are optional and extend Pulse functionality. The Manager automatically updates the Custom Resource (CR), and the Pulse Operator deploys the services on the Kubernetes cluster.
Add the Add-on Services You Want to Deploy
Add the required services to the list in the API request. The following add-on services are available:addons
Add-on Service | Component Identifier |
Core Connectors | |
SparkStats | |
Kafka Connector | |
Ozone Connector | |
FS Analytics V2 | |
Oozie Connector | |
Impala Connector | |
Druid Analyzer | |
SQL Analyzer | |
Trino Connector | ad-trino-connector |
Send the API Request
Use the following command to deploy the services. Replace the placeholders as described below.curl
curl --request PUT \
--url http://<Ingress API for the Manager Server>/api/v1/mserver/deploy/addons/<clustername> \
--header '<basic credentials>'
--header 'Content-Type: application/json' \
--data '{
"addons": [
"CORE CONNECTORS",
"SPARKSTATS",
"KAFKA CONNECTOR",
"OZONE CONNECTOR"
.
.
.
],
"extra_hosts": {
"<IP Address 1>": "<host name 1>",
"<IP Address 2>": "<host name 2>",
"<IP Address 2>": "<host name 3>",
"<IP Address 3>": "<host name 4>",
}
}'
Update the file to include the add-on services needed for your specific cluster.addons.json
Replace Placeholder Values
Placeholder | Description |
| URL exposed through Ingress for the Pulse Manager service |
| Name of the cluster where you are deploying add-on services |
addons | List of add-on component identifiers (see Step 1) |
extra_hosts | IP-to-hostname mappings used for internal networking |
What Happens Next
- The Pulse Manager Server receives the API request and updates the Custom Resource.
- The Pulse Operator automatically deploys the specified add-on services to your Kubernetes cluster.

Have a suggestion?