1

I have installed apache pulsar using helm chart in AWS EKS,
Reference : Apache Pulsar Helm Deployment on Kubernetes

also enabled pulsar manager and deployed pulsar manager UI, all pods are up and running, when i open pulsar manager UI in browser using load balancer external IP, Manager UI is loading but unable to login using default username and password, also unable to get CSRF token

Pulsar manager

When i do curl, getting 404 not found error from pulsar manager Pulsar manager : v0.3.0

CSRF_TOKEN=$(curl http://pulsar-load-balancer-ip:9527/pulsar-manager/csrf-token)
Vishwanath M
  • 11
  • 2

2 Answers2

0

Are there any errors in the logs? Are the external IPs exposed?

what are the results of kubectl get nodes?

is everything running?

kubectl get pods -w -l app=pulsar

https://github.com/apache/pulsar-manager

he default values will create a ClusterIP for the Pulsar Manager you can use to interact with cluster. To find the IP address of the Pulsar Manager, use the following command:

kubectl get service -n After find the ip address of the Pulsar Manager, you can access the Pulsar Manager at http://${pulsar-manager-cluster-ip}/#/environments.

Tim Spann
  • 517
  • 2
  • 6
0

The backend service may not complete starting for some reason enter the container by command "kubectl exec" and see log

Antares
  • 1
  • 1