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 kubectl access 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:

Bash
    
xxxxxxxxxx
 
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo update
Copy

Install NGINX Ingress Controller

Install the NGINX Ingress Controller in the ingress-nginx namespace:

Bash
    
xxxxxxxxxx
 
helm install ingress-nginx ingress-nginx/ingress-nginx \  --namespace ingress-nginx \  --create-namespace
Copy

Verify the External IP Address

Run the following command to verify that the Ingress Controller service has an external IP address:

Bash
    
xxxxxxxxxx
 
kubectl get svc -n ingress-nginx
Copy

Expected output:

Bash
    
xxxxxxxxxx
 
NAME                                 TYPE           CLUSTER-IP      EXTERNAL-IP     PORT(S)                      AGEingress-nginx-controller             LoadBalancer   10.200.28.177   34.14.141.148   80:30946/TCP,443:31828/TCP   27hingress-nginx-controller-admission   ClusterIP      10.200.21.233   <none>          443/TCP                      27h
Copy

Create the Ingress for Pulse Backend Services

Create a file named ingress.yaml with the following content:

Bash
    
xxxxxxxxxx
 
apiVersion: networking.k8s.io/v1kind: Ingressmetadata:  name: pulse-ingress  namespace: pulse  annotations:    nginx.ingress.kubernetes.io/use-regex: "true"    nginx.ingress.kubernetes.io/rewrite-target: /$2spec:  ingressClassName: nginx  rules:  - http:      paths:       - path: /manager(/|$)(.*)        pathType: ImplementationSpecific        backend:          service:            name: accelo-manager            port:              number: 20001       - path: /streaming(/|$)(.*)        pathType: ImplementationSpecific        backend:          service:            name: ad-streaming            port:              number: 19005       - path: /hydra(/|$)(.*)        pathType: ImplementationSpecific        backend:          service:            name: ad-hydra            port:              number: 19072       - path: /axnserver(/|$)(.*)        pathType: ImplementationSpecific        backend:          service:            name: ad-axnserver            port:              number: 19999            - path: /profiler(/|$)(.*)        pathType: ImplementationSpecific        backend:          service:            name: ad-pulse-profiler            port:              number: 19029
Copy

Change namespace to your own namespace.

Apply the file:

Bash
    
xxxxxxxxxx
 
kubectl apply -f ui-ingress.yaml
Copy

Verify the Ingress Configuration

Run the following command:

Bash
    
xxxxxxxxxx
 
kubectl get ingress -n pulse
Copy

Confirm that both pulse-ingress and pulse-ui-ingress are created successfully.

Access the Pulse UI

Use the external IP address of the ingress-nginx-controller service to access Pulse.

Example:

Bash
    
xxxxxxxxxx
 
http://<EXTERNAL-IP>
Copy

Replace <EXTERNAL-IP> with the external IP address displayed in the kubectl get svc -n ingress-nginx output.

Last updated on

Was this page helpful?