-
Notifications
You must be signed in to change notification settings - Fork 173
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
Tiny-Kafka example doesn't work #41
Comments
Thanks I saw that too recently, it's (ironically) an inconsistency in how helm creates the tarball name now that we've switched to helm generating / pulling vs us manually pulling them. This will actually be resolved more completely by #16 and the native-k8s-apply branch. |
jeff-mccoy
added a commit
that referenced
this issue
Sep 16, 2021
…inconsistencies-breaks-some-charts Fixes #41, ensure standard naming for downloaded helm charts
jeff-mccoy
added a commit
that referenced
this issue
Feb 8, 2022
Signed-off-by: Jeff McCoy <code@jeffm.us>
Noxsios
pushed a commit
that referenced
this issue
Mar 8, 2023
Signed-off-by: Jeff McCoy <code@jeffm.us>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Tiny-Kafka example doesn't work.
zarf package create
works fine, but when runningzarf package deploy
I get the error message:Digging deeper, it looks to be because the .tgz file that Strimzi publishes is actually named
strimzi-kafka-operator-helm-3-chart-0.24.0.tgz
, and that's what gets saved in the tarball, but Zarf expects the chart files to be named<ChartName>-<Version>.tgz
I'm submitting a PR to fix the example by pulling it down under
files:
instead ofcharts:
but it's just a bandaid fix and deserves to be looked at more closely.The text was updated successfully, but these errors were encountered: