Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pulsar Helm Chart Initialization Failure When Using Existing Secret #512

Open
robertdumitrescu opened this issue Jul 24, 2024 · 1 comment

Comments

@robertdumitrescu
Copy link

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'
  1. Deploy the Helm chart.
  2. 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.

@Mortom123
Copy link
Contributor

Can you post some logs from kubectl / k9s of the init pod and see why it fails?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants