Open MatthiasLohr opened 3 years ago
Maybe best to close, due to the introduced kubernetes.yaml and related documentation?
In my opinion, static kubernetes manifests have major disadvantages compared to a Helm chart. Also, the kubernetes manifest has several questionable design decisions (e.g., service type LoadBalancer). Therefore I still will use a / my helm chart for verapdf deployment and would encourage others to do so as well.
I mean, everybody is of course free to use this kubernetes.yaml file, but the only thing I suggest is that a user knows about an existing and maintained helm chart. So, no reason not to link it?
A while back I was also working on a kubernetes deployment of the rest demonstrator, and needed a helm chart. I had forked the project for my own personal use. I have made a PR with the chart if you would like to take a look @MatthiasLohr ?
https://github.com/veraPDF/veraPDF-rest/pull/154
Its basically a boilerplate chart with the specifics of the image added. There is certainly room for improvement, my fork used github actions to push tagged images to ghcr.io with these reflected in the helm chart, as it seems like only a recent addition to the current upstream project.
@darrendignam, I provided some comments. However, you can also feel invited to participate in my chart, https://gitlab.com/MatthiasLohr/verapdf.
Hi folks,
I wrote a Kubernetes Helm Chart to run the
verapdf/rest
image on your own Kubernetes cluster. Maybe you are interested in linking to it?The repository URL ist https://gitlab.com/MatthiasLohr/verapdf, and it's also included in the official Helm Chart directory, ArtifactHub: https://artifacthub.io/packages/search?page=1&ts_query_web=verapdf
Best regards Matthias