-
Notifications
You must be signed in to change notification settings - Fork 232
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 init pod "Missing required options" #569
Comments
@MiraculousNightingale pulsar-helm-chart/charts/pulsar/templates/pulsar-cluster-initialize.yaml Lines 120 to 155 in e55405c
I don't see how there could be an extra line feed unless Helm is somehow injecting it. Which Helm version ( helm version ) are you using? In CI, we test with 3.12.0 and 3.14.4.What OS do you use? Which k8s server version? ( kubectl version )Helm supported version skew documentation. (Pick a Helm version that supports your k8s server version to be sure that it's compatible.) |
I'm facing the same issue... |
@brunocascio Thanks. It looks like the fix #166 was reversed in a recent PR, https://github.com/apache/pulsar-helm-chart/blame/e55405cbe2819647f1a642a850364f17544603b0/charts/pulsar/templates/pulsar-cluster-initialize.yaml#L122 I'll fix it. |
PR to fix the issue is #572 |
Thanks @lhotari ! 🚀 Is there any ETA for bump the new chart version? Thanks again |
@brunocascio In about 2 weeks. I'm currently working on Pulsar 3.0.10, 3.3.5 and 4.0.3 release candidates and if there aren't delays, the release for these Pulsar releases would happen on Feb 26th. I'll start the next pulsar-helm-chart release after this with Pulsar 4.0.3 as the default. It takes about 1 week to complete the release due to ASF release policy where release voting has to happen for every release. |
Thanks @lhotari ! |
Description
When deploying pulsar helm chart, pulsar init pod fails with the following error:
Reproduction steps
Expected behavior
Pulsar-init pod executing successfully.
Additional context
Chart version: 3.9.0
Describing pulsar-init pod shows an empty line in the args. That seems to be the reason for the error. Why does it appear there?
The text was updated successfully, but these errors were encountered: