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 manager always uses default user/password #108

Closed
sloan-dog opened this issue Mar 15, 2021 · 4 comments · Fixed by #219
Closed

Pulsar manager always uses default user/password #108

sloan-dog opened this issue Mar 15, 2021 · 4 comments · Fixed by #219

Comments

@sloan-dog
Copy link

Expected behavior

Providing non default username and password for Pulsar Admin Manager component should actually change the username and password

Actual behavior

Pulsar admin manager always uses the default username and password (not secure)

Steps to reproduce

helm upgrade --install --set pulsar_manager.admin.password=myspecialpassword --set pulsar_manager.admin.user=myspecialuser --set initialize=true --values examples/values-minikube.yaml --namespace pulsar pulsar-mini apache/pulsar

*I am aware that default chart does not restart pods if the secret changes, but lets say this is fresh install (also the case).

System configuration

Helm chart commit: c059ea2

Using all default values for minkube

@jeantil
Copy link
Contributor

jeantil commented Mar 16, 2021

hi @sloan-dog , this report looks a lot like #31 to me :)

lhotari added a commit to lhotari/pulsar-helm-chart that referenced this issue Jan 26, 2022
…default

Fixes apache#31
Fixes apache#108

- disable pulsar_manager by default because of security reasons

- set properties compatible with pulsar-manager v0.2.0,
  https://github.com/apache/pulsar-manager/blob/v0.2.0/src/main/resources/application.properties#L87-L91

- remove obsolete environment variables
@lhotari
Copy link
Member

lhotari commented Jan 26, 2022

Please review PR #212, it should fix this issue.

@mkoertgen
Copy link

Hi @lhotari ,

As a workaround, I managed to create a simple k8s-job that performed the steps described in

Here is the gist of it:

Please have a look. It should be straight-forward to add it to the helm chart as a post-install helm-hook

Note: Not sure whether the pod also needs to persist state. Might be the configuration gets lots on restarts (not sure where this is persisted).

@lhotari
Copy link
Member

lhotari commented Feb 14, 2024

solved by #457

@lhotari lhotari closed this as completed Feb 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants