Title
Create new category
Edit page index title
Edit category
Edit link
Set Up Pulse Databases
Pulse supports multiple database deployment models for Kubernetes environments.
Choose the database deployment model that matches your infrastructure requirements.
Database Deployment Options
Deployment Model | Description |
|---|---|
External database nodes | Deploy Pulse database services on dedicated virtual machines (VMs) or bare-metal hosts. Use this option when database services are managed outside the Kubernetes cluster. |
Kubernetes-based deployment | Deploy Pulse database services within the Kubernetes cluster by using Helm charts. Use this option when you want to manage database services as Kubernetes workloads. |
Choose a Deployment Model
Deploy databases on dedicated VMs or bare-metal hosts
Use this deployment model when Pulse runs on Kubernetes and the database services run on separate hosts.
Set up PulseManager Agent on the database hosts. For details, see Deploy Pulse Manager Agent.
Setting up the PulseManager service on database hosts does not deploy the database containers. Deploy the database containers separately from the Accelo Manager workflow.
Deploy databases on Kubernetes
Use this deployment model when database services run within the Kubernetes cluster.
For details, see Deploy Pulse Databases via Helm.
For additional help, contact www.acceldata.force.com OR call our service desk +1 844 9433282
Copyright © 2026