Marcel Körtgen

Kind of similar problem for me. Reinstalling a pulsar cluster chart=2.7.7 with initialize=true results in brokers / proxies getting stuck waiting for zookeeper.  I could track it down to...

To me it looks like the problem has to do with helm-templates expanding empty lines without breaks (`\`) causing the shell call to fail. Here is what the helm renders...

Strange, because the helm-template looks fine to me. I have no idea where this extra line is coming from - https://github.com/apache/pulsar-helm-chart/blob/master/charts/pulsar/templates/pulsar-cluster-initialize.yaml#L92 Git blame tells no changes there for about the...

Probably, a suggestion for the future: Would it not be possible to default the `initialize=true`-value from [Helm's builtin-objects](https://helm.sh/docs/chart_template_guide/builtin_objects/) like `{{- if .Release.IsInstall }}` ?

@lhotari Good point. I will check today with upgrading to 2.7.8.

Hi @lhotari , As a workaround, I managed to create a simple k8s-job that performed the steps described in - https://pulsar.apache.org/docs/en/administration-pulsar-manager/#set-administrator-account-and-password Here is the gist of it: - https://gist.github.com/mkoertgen/a3c45689e78b88f71d2c373a243c95d7 Please...

Probably removed because most clusters will typically already have a similar daemonset? As a workaround can we just deploy a standard node-exporter? - https://github.com/prometheus-community/helm-charts/tree/main/charts/prometheus-node-exporter

Added as mentioned above with `podAnnotations.scrape: true`. This kind of works but lacks the `kubelet_volume_stats_*` metrics which were helpful in monitoring e.g. the ledger-usage of the bookies. Some of the...

Having the same issue with OOMKilled and with the information from #192 pinned it down to large helm-repo of bitnami with index-file alone having 13.4M 

Thanks for the documentation link @stefanprodan. That was helpful. Removing bitnami-helm-repos in redundant namespaces brought down the mem-footprint to 190M, yet still peaking every 10min (helm repo update interval) ...