Bernd Schorgers
Bernd Schorgers
The upgrade to v5.0.0 of the vaultwarden chart was a breaking change because of the changes to the underlying database dependency charts. Without seeing your actual Helm values it is...
> I didn't read anything about breaking changes respectively about how to upgrade to a newer version of k8s-at-home/vaultwarden. The vaultwarden version hasn't changed recently. The last image bump was...
We've bumped the image version to v1.10. We've not yet looked at the env vars though.
I just checked, and we don't set any value for the env var, not even an empty string: the output of `helm template k8s-at-home/teedy` gives this: ```yaml env: - name:...
We would all like that. But since our charts currently target older versions we are not (yet) able to do so. But as usual, PR's (instead of oneliner issues) are...
@utegental please fix the issue title
[mealie] api container missing health checks, causes service to go ready before it can serve traffic
By default our charts only check if a single port is able to connect, in this case the frontend. Ideally the frontend wouldn't report 'ready' if the api is not...
[mealie] api container missing health checks, causes service to go ready before it can serve traffic
You are right, I somehow had it in my mind that the probes are per Pod 🤦
Do you happen to have `https://github.com/k8s-at-home/charts/blob/master/charts/stable/homer/values.yaml#L50`enabled? In that case the `config` persistence item would be overwritten by the configured configMap. I'll add a note to the README about this behavior...
Thanks for taking the time to write up this issue. Exposing metrics / serviceMonitor is not a feature of the common library though, so this repo is not the correct...