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

Change Pulsar Manager docker image version #85

Closed
dadacom379 opened this issue Nov 20, 2020 · 2 comments
Closed

Change Pulsar Manager docker image version #85

dadacom379 opened this issue Nov 20, 2020 · 2 comments

Comments

@dadacom379
Copy link

When activating JWT token authentication the Pulsar manager is not connecting to broker. The manager image v0.1.0 does not support JWT configuration.

In the new version v0.2.0 the support is there:

The solution is to change the docker version of the docker images from the helm chart.

The actual config in helm chart version pulsar-2.6.2-1 :
image

The correction should look like:
image

@dadacom379 dadacom379 changed the title Change Pulsar Manager docker image Change Pulsar Manager docker image version Nov 20, 2020
@jeantil
Copy link
Contributor

jeantil commented Mar 16, 2021

I found this issue while looking into #31 and #108
Since the tag version is in values.yml you can use --set images.pulsar_manager.tag=v0.2.0 to upgrade the version
like so

helm install --set images.pulsar_manager.tag=v0.2.0 --set initialize=true --set create_namespace=true --values examples/values-minikube.yaml --namespace pulsar pulsar-mini apache/pulsar

not sure if that will solve your issue but it's worth a shot

@lhotari
Copy link
Member

lhotari commented Jan 26, 2022

The docker image version was upgraded as part of #206.

@lhotari lhotari closed this as completed Jan 26, 2022
pgier pushed a commit to pgier/pulsar-helm-chart that referenced this issue Apr 22, 2022
…he#85)

- it shouldn't be required when spec.publishNotReadyAddresses: true
  (or the legacy annotation service.alpha.kubernetes.io/tolerate-unready-endpoints: "true") is used
  for the headless service
- triggers issue "ZOOKEEPER-2164: Quorum members can not rejoin after restart"
  - fixed in ZK since 3.5.8
- quorumListenOnAllIPs is considered an unsafe option in Zookeeper
  https://zookeeper.apache.org/doc/current/zookeeperAdmin.html#Unsafe+Options
rdhabalia pushed a commit to rdhabalia/pulsar-helm-chart that referenced this issue Feb 2, 2023
* [cms-6674]: add security context

* [cms-6674]: add defaults in values.yaml

* [cms-6674]: cleanup athenz n cameo def

* [cms-6674]: cleanup athenz n cameo def

* [cms-6674]: cleanup athenz n cameo def

* [cms-6674]: fix sia n cameo image def

* [cms-6674]: fix sia n cameo image def

* [cms-6674]: fix sia n cameo image def

* [cms-6674]: fix athenz n cameo in ar, bookie

* [cms-6674]: fix indent

* [cms-6674]: fix indent

* [cms-6674]: fix duplicate values

* [cms-6674]: remove sia n cameo container from initialize

* [cms-6674]: fix athenz n cameo in brk, logs, pinit

* [cms-6674]: fix athenz n cameo in brk, logs, pinit

* [cms-6674]: fix athenz n cameo in brk, logs, pinit

* [cms-6674]: fix athenz n cameo in brk, logs, pinit

* [cms-6674]: fix athenz n cameo in tlset,ts

* [cms-6674]: fix athenz n cameo in tlset,ts

* [cms-6674]: fix athenz n cameo in zk

* [cms-6674]: cleanup

* fix: yamls

* fix: ts security context

* [cms-6674]: fix yamls
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

3 participants