Trino helm chart
They added catalogs in their chart, have a look at this pull request https://github.com/trinodb/charts/pull/1
I found some interesting tips in the Trino slack channel. I am quoting Karthik below:
There are two options
- creating catalog files using config maps, if you take this route then when ever you need to add new catalogs you need to rebuild your images.
- create a persistent volume and attach the volume to docker container, this PV can be anything (NFS, S3 etc) and store catalogs here, so when you add catalogs you just need to restart the server but no need to rebuild the image
I am new to Kubernetes deployments and will be experimenting with the aforementioned approach.