Closed Tan-tan-san closed 7 months ago
Hey @Tan-tan-san, thank you for your issue. I am currently working on an automated solution to update charts in accordance with upstream changes, however it's going to take a bit more time.
However I think you're under misconception here, you have access to the entire tika chart values under the tika
key. Even though I only configure tika.enabled
in my values.yaml you can modify the entire chart's values by just appending to the tika
object. To modify the image tag just add the tika.image.tag
YAML value. Have a look at this file in the Helm documentation for more information on how subcharts inherit values from the parent's values.yaml file. You can use helm show values <tika-repo>/tika
to view the entire charts values.
LMK if this helped! 👍
That should get me sorted for now, thanks! Glad its on your radar and look forward to the solution when you get the time. Thanks for responding too!
Name and Version
fmjstudios/paperless-ngx:latest
What is the problem this feature will solve?
The tika container image tag is hardcoded and doesnt allow me to use a later version that supports ARM64.
What is the feature you are proposing to solve the problem?
Adding the ability to change the tika container image tag will allow me to deploy this chart using a newer tag, that allows ARM64 support.
What alternatives have you considered?
I've manually edited the manifest and deployed successfully, but I would much rather deploy this helm chart via argocd as an application manifest and keep the deployment within my CI/CD pipeline.