Title
Create new category
Edit page index title
Edit category
Edit link
Configure Ingress for Pulse on Kubernetes in GKE
Use this procedure to configure NGINX Ingress for Pulse services deployed on a Kubernetes cluster in Google Kubernetes Engine (GKE).
Prerequisites
Before you begin, ensure that:
Pulse is deployed on the Kubernetes cluster.
You have
kubectlaccess to the target cluster.Helm is installed and configured.
The Pulse services are available in the target namespace.
The examples in this procedure use the pulse namespace. Replace pulse with your namespace, if different.
Add the NGINX Ingress Helm Repository
Run the following commands:
Install NGINX Ingress Controller
Install the NGINX Ingress Controller in the ingress-nginx namespace:
Verify the External IP Address
Run the following command to verify that the Ingress Controller service has an external IP address:
Expected output:
Create the Ingress for Pulse Backend Services
Create a file named ingress.yaml with the following content:
Change namespace to your own namespace.
Apply the file:
Verify the Ingress Configuration
Run the following command:
Confirm that both pulse-ingress and pulse-ui-ingress are created successfully.
Create the Ingress for the Pulse UI Service
Create a file named ui-ingress.yaml with the following content:
Apply the file:
Access the Pulse UI
Use the external IP address of the ingress-nginx-controller service to access Pulse.
Example:
Replace <EXTERNAL-IP> with the external IP address displayed in the kubectl get svc -n ingress-nginx output.
For additional help, contact www.acceldata.force.com OR call our service desk +1 844 9433282
Copyright © 2026