Closed palmergw closed 2 years ago
Are you able to deploy any other chart in our repository? This smells like a Rancher issue but I want to confirm.
I am suspecting the same thing, since the chart does not seem to contain any hardcoded overrides.
I am able to deploy other charts from your repo no problem. What I noticed about this chart being different from the others, is that it loads a default chart like below:
env:
TZ: UTC
image:
pullPolicy: IfNotPresent
repository: ghcr.io/advplyr/audiobookshelf
tag: null
ingress:
main:
enabled: false
persistence: null
service:
main:
ports:
http:
port: 80
While other charts are often <parameter>: {}
instead of null. This doesn't mean it's NOT a Rancher issue, or even a Helm issue, but I had such success with other charts my mind didn't run there first.
I do know that none of the other charts I've tried have specifically had persistence as null, or even an empty object if I recall correctly.
Changes to env or image do stick.
I've just submitted a potential fix, hopefully this fixes your issue. Please feel free to re-open this issue if the problem still occurs.
Worked like a charm. Thanks so much!
Helm chart name
audiobookshelf
Helm chart version
1.1.1
Container name
ghcr.io/advplyr/audiobookshelf
Container tag
2.0.10
Description
Values specified in the persistence section of the values yaml are ignored and overwritten.
Expected result
When specifying persistence values, they should be respected and not removed from the deployed chart.
Helm values to reproduce
Additional Information
Immediately upon deploying in Rancher, inspecting the yaml for the installed application shows that persistence values have been nulled out, which is the default for this chart.
name: audiobookshelf namespace: default resources: