I'm using kroki with k3s, and I followed instructions as stated in docs.
I found that the yamls used in k8s deployment is maintained as a zip file at kroki-k8s-multipod.zip.
However, it doesn't keep up to date with kroki updates, i.e, in kroki 0.22.0, yamls for blockdiag is not needed.
So I suggest to move these k8s yamls into a folder instead of putting them in a zip file, and adjust the CI to publish them as a asset of a release.
Moreover, if we can publish these yaml as a helm chart, that would be nice.
I'm using kroki with k3s, and I followed instructions as stated in docs. I found that the yamls used in k8s deployment is maintained as a zip file at kroki-k8s-multipod.zip. However, it doesn't keep up to date with kroki updates, i.e, in kroki 0.22.0, yamls for blockdiag is not needed. So I suggest to move these k8s yamls into a folder instead of putting them in a zip file, and adjust the CI to publish them as a asset of a release. Moreover, if we can publish these yaml as a helm chart, that would be nice.