[Question] Helm install is broken (Strimzi 0.17.0)
See original GitHub issueHello!
Currently we are using strimzi 0.16.2 which works perfectly fine, we have tried to upgrade to 0.17.0 and we are getting following, seems like there is an issue with helm:
+ helm repo add strimzi http://strimzi.io/charts/
"strimzi" has been added to your repositories
+ helm upgrade --reuse-values --install strimzi strimzi/strimzi-kafka-operator --version=$STRIMZI_VERSION --namespace=kafka --set nodeSelector.nodegroup-type=kafka
UPGRADE FAILED
Error: render error in "strimzi-kafka-operator/templates/050-Deployment-strimzi-cluster-operator.yaml": template: strimzi-kafka-operator/templates/_kafka_image_map.tpl:34:40: executing "strimzi.kafka.image.map" at <.Values.kafkaMirrorMaker2.image.repository>: nil pointer evaluating interface {}.image
Error: UPGRADE FAILED: render error in "strimzi-kafka-operator/templates/050-Deployment-strimzi-cluster-operator.yaml": template: strimzi-kafka-operator/templates/_kafka_image_map.tpl:34:40: executing "strimzi.kafka.image.map" at <.Values.kafkaMirrorMaker2.image.repository>: nil pointer evaluating interface {}.image
Any ideas ?
Thanks!
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
Strimzi Documentation (0.17.0)
Deploying the Cluster Operator using Helm Chart. Prerequisites. Helm client has to be installed on the local machine. Helm has to be installed...
Read more >strimzi-kafka-operator 0.17.0 - Artifact Hub
Parameter Description Default
image.repository Cluster Operator image repository strimzi
image.name Cluster Operator image name cluster‑operator
image.tag Cluster Operator image tag 0.17.0
Read more >September 2021 update - Flux CD
News in the Flux family. Flux 0.17.0. We have released Flux v0.17.0. You will be pleased to learn that this version has no...
Read more >Strimzi kafka connect with debezium mongodb-connector not ...
And i am receiving the schema changes whenever i add or update a record in table of inventory database. Issue: This whole setup...
Read more >hashicorp-terraform/Lobby - Gitter
resource "helm_release" "strimzi" { count = var.enabled ? ... chart = "strimzi-kafka-operator" version = "0.17.0" name = "kafka_operator" namespace ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Any improvements to the readme or to the docs are always welcomed. Thanks for helping with this issue.
@klalafaryan, yes, that would make sense. I’m used to using charts that do an
auto-sync
based on the platform you are using. I found this issue mentioning the same strategy. Also, they mentioned that this is a good feature candidate for Helm 3, but, I couldn’t find any relevant issue opened for that yet.@scholzj, I think this issue can be closed. Even though it’s common practice to run
helm repo update
beforehelm install
, do you think it would be beneficial to update the relevant README with a tip/note? I can slip that in the https://github.com/strimzi/strimzi-kafka-operator/pull/2979 PR.