common Helm library.
Yeah that logic was in the wrong place, that was meant for the Frontend container to "learn" what the API URL was. Fixed: https://kolaente.dev/vikunja/helm-chart/commit/3ea99647e2b2343762d9fe7ce26…
common Helm library.
Fair, forgot to use the ingress value for that variable as well. I went ahead and fixed it. I also included a comment to to the user incase they aren't using an ingress resource (I was even…
common Helm library.
LOL, I've gotta say, that explains a lot about my own Vikunja deployment after realizing that /api/v1 returns a 401...
fixed!
common Helm library.
The existing chart has “chart-example.local”, I figured that changing that to “vikunja.local” would be more Vikunja “branded”, if you will, lol.
I can change it back if you would…
common Helm library.
@konrad should be ready for another readthrough whenever you're free, I'm confident this now both works and delivers on expectations.
common Helm library.
I mean upgrading from the current chart to the new one.
I see what you're saying - from a user's perspective, what is updating to this version of the Helm chart like. It will definitely…
common Helm library.
I'm also trying to add some comments to the values.yaml so that a user is less lost when trying to use the Helm chart. I also intend to update the README.md.
common Helm library.
I went ahead and removed it, the user can add it to each pod as they see fit :)
common Helm library.
Are you phasing out VIKUNJA_API_URL by chance? I don't see it at https://vikunja.io/docs/config-options/, but I still see it in the injector.sh for the Docker container...
common Helm library.
I like the general idea of making the chart simpler.
What about the upgrade path?
Not only does it make it simpler, it also allows the user to add/modify the values.yaml to include…
common Helm library.
It's a Kubernetes "non-human" user, a Kubernetes-specific object.
ServiceAccount objects in Kubernetes serve several purposes within the cluster:
- Provide a distinct identity:…
common Helm library.
Upgrade path (like upgrading to newer versions of Vikunja) would just require a user to reference a newer version of the image at the top of values.yaml.