Comments (4)
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?
from pulsar-helm-chart.
You can try @streamvisor as an enterprise-grade alternative to pulsar-manager. It's free :)
from pulsar-helm-chart.
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.
from pulsar-helm-chart.
Fixed by #457
from pulsar-helm-chart.
Related Issues (20)
- Requires AWS access/secret key when offload driver is set to aws-s3 HOT 2
- not able to login to pulsar UI HOT 7
- No data shown in Grafana Dashboards HOT 2
- Pulsar Manager v0.4.0 in kubernetes still can not persist any data HOT 1
- Argo CD unable to generate template with pulsar chart 3.3.0 HOT 5
- Deployment using JWT authentication + Function Worker is not working properly HOT 1
- [Bug] Broker startup could get into a long crash loop when Functions are enabled HOT 1
- Allow using a separate volume for the zookeeper transaction log
- Allow specifying an existing secret for pulsar-manager credentials
- Make it possible to optionally override .ReleaseIsInstall logic in init jobs
- Latest chart version: 3.4.0 missing in the Apache helm repo index HOT 3
- Plugins support HOT 1
- PKIX path building failed: unable to find valid certification path to request to requested target HOT 2
- HPA missing namespace HOT 1
- upgrade to pulsar helm chart version 3.3.1 from 2.9.4->3.0.0->3.3.1 with the pulsar-broker error HOT 2
- Pulsar manager service fails saying "2024-05-07 15:02:17,476 INFO exited: pulsar-manager-backend (terminated by SIGKILL; not expected)" HOT 2
- Allow broker's service clusterIP customisation: headless vs non-headless HOT 1
- pulsar-broker failed to start with both Liveness probe and Readiness probes failed: HTTP probe failed with statuscode: 404 HOT 5
- Specifying image pull policy in the chart HOT 1
- Setting up custom config HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pulsar-helm-chart.