Matt Baker
Matt Baker
Maybe you default to rootless with the CLI flag to swap back for those who may want that for whatever oddball reason?
At the very least setting existing secrets for external DB connections should be supported in values.yaml
We're seeing this too.
Any movement on this? I'm having to do a pretty hacky workaround for this and it'd be nice if the helm chart actually put everything in the release namespace properly.
Bump and second @mgeggie's comment - please reopen this issue. Not supporting AWS RDS for a core component of Grafana isn't really an option.
Still an issue.
I don't think wrapping a GUI tool in a shell call is a long term fix for this. It's a short term workaround sure, but I'd like to see this...
I'm experiencing this exact problem - it'd be very nice for `spec.ingressClassName` to work as expected here - it's what basically every helm chart in existence has hooks into for...
I think this should be reopened - having to spawn this via a shell isn't very intuitive for something that's intended to be a GUI tool.