Pulsar default password not working

[kssanthosh]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. I have used helm chart

helm repo add apache https://pulsar.apache.org/charts

helm repo update

helm install pulsar apache/pulsar --timeout 10m --values values.yaml --version 3.0.0

Using values.yaml

values.txt

5. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]

Additional context
Add any other context about the problem here.

[ton3r]

If you have the same problem like me, than you will have a 404 Error in the WebConsole during Login.

During my debug, I found out that this is ok. Because the Backend didn't start.

After connecting to the shell of ird-pulsar-pulsar-manager I've seen in the tail -f pulsar_manager.log of the spring instance that it can't connect to postgres on 127.0.0.1. There wasn't any available.

Installing apt-get update && apt-get -y install procps lsof vim and I was possible to figure out that there was nothing listening on port 7750 or 5432

So I've created my own postgres instance somewhere, create the schema with this link and startet the helm install like

helm install \
    --values pulsar-ird/values.yaml \
    --set initialize=true \
    --set proxy.ports.http=8080 \
    --set proxy.securityContext.runAsUser=0 \
    --set proxy.securityContext.runAsGroup=0 \
    --set proxy.service.loadBalancerIP=192.168.77.101 \
    --set pulsar_manager.admin.user=postgres \
    --set pulsar_manager.admin.password=POSTGRES_PASSWORD \
    --set pulsar_manager.configData.URL=jdbc:postgresql://192.168.77.10:5432/pulsar_manager \
    --set pulsar_manager.service.loadBalancerIP=192.168.77.100 \
    --namespace pulsar \
    ird-pulsar apache/pulsar

I've to switch the proxy to 8080 because bind to 80 wasn't possible. Also the possible "solutions" setting the runAs* parameter to root didn't help. So I take port 8080.

After the helm command is finished, I connect to the shell again and tail -f pulsar_manager.log again. Look out for Hikari Logs. That went well.

After the spring service started up and was listening on 7750 I was possible to create an admin user! Yes! You need this. It's not directly documented by the how tos!! #crazy

CSRF_TOKEN=$(kubectl get secret --namespace pulsar ird-pulsar-token-admin -o jsonpath="{.data.TOKEN}" | base64 -d)
curl \
    -H "X-XSRF-TOKEN: $CSRF_TOKEN" \
    -H "Cookie: XSRF-TOKEN=$CSRF_TOKEN;" \
    -H 'Content-Type: application/json' \
    -X PUT http://THE_MANAGER_IP:9527/pulsar-manager/users/superuser \
    -d '{"name": "admin", "password": "BirnenBurner123_", "description": "test", "email": "[email protected]"}'

Then you should be able to login with admin:BirnenBurner123_

In the end I am still struggling to set my desired internal IPs. They got ignored and always got new ip's on re-deploys.

And fun-fact : pulsar_manager.admin.user and pulsar_manager.admin.password are the db access credits (may be also some credits for other things..)

So my question is here : What is the definition of "production ready" ? And why uses the pulsar_manager by default in internal postgres instance (which is not starting up) in a non-stateful-set?

[alpreu]

You can try @streamvisor as an enterprise-grade alternative to pulsar-manager. It's free :)

[lhotari]

You can try @streamvisor as an enterprise-grade alternative to pulsar-manager. It's free :)

@alpreu please don't spam Apache issue tracker with advertisements.

[lhotari]

Fixed by #457