robertdumitrescu opened a new issue, #512:
URL: https://github.com/apache/pulsar-helm-chart/issues/512
**Describe the bug**
The Pulsar Helm chart fails to initialize the pulsar-manager-init pod when
the existingSecret feature is used. The initialization process gets stuck,
preventing the pod from starting, and the CSRF token becomes unusable, leading
to 404 errors during login attempts.
**To Reproduce**
Steps to reproduce the behavior:
1. Configure the Helm chart to use an existing secret
```
pulsar_manager:
admin:
existingSecret: 'some-secret-name'
```
2. Deploy the Helm chart.
3. Observe the pulsar-manager-init pod status.
**Expected behavior**
The pulsar-manager-init pod should initialize correctly, and the job should
complete successfully. The CSRF token should be usable, and login requests to
Pulsar Manager should not return 404 errors.
**Additional context**
This issue occurs when trying to use the existingSecret feature to avoid
hardcoding credentials in values files. The initialization of the
pulsar-manager-init pod fails, causing subsequent CSRF token and login requests
to return 404 errors.
the pulsar-manager-init pod no longer initializes, being stuck in
PodInitializing. Additionally, the job does not finish, and the CSRF token
becomes unusable, resulting in 404 errors when attempting to log in to Pulsar
Manager for both the CSRF token and POST login request.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@pulsar.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
