
Trino is deployed everywhere – on-premise, in private data centers, in the cloud with hosting providers, on bare metal servers, on virtual machines, and with containers. With all these options for deployments, a Kubernetes-based platform with a container emerged as the most widely used approach.
The Trino project caters for this usage with our container images for every release and our Helm chart. However we keep hearing from people who want to use a Kubernetes operator…
Existing operators #
We know that various companies have Kubernetes operators developed internally, and we also know that open source ones exist, for example:
- trino-operator from Stackable with integration in trino-lb
- Charmed Trino K8s Operator from Canonical
Ideally these separate efforts can combine their work, and create a great operator in the Trino project that is closely aligned with Trino itself, and also suitable for future integration with Trino Gateway. In fact, the Trino Gateway is a good example where different parties came together and considerably innovated together. Hopefully we can achieve the same with the operator. It can still be expandable and modular to suite for specific needs on different platforms and for different users.
We also know that this is a long standing community wish from the issue and various discussions with users.
Discussing next steps #
However there are some complications such as choice of programming language or commitment to help within the Trino project as subproject maintainer. We kicked off some of these discussion in the past at Trino contributor meetings, and hope that now is a good time to continue.
To that end we are arranging a community meeting:
- Virtual video call
- 30th of October 2024
- 8:00 PDT / 11:00 EDT / 15:00 GMT / 16:00 CET
- Invite available from Manfred on Trino Slack or via email:
We will also post connection details on the #kubernetes channel and we are collecting related discussion points on our contributor meeting page.
Looking forward to a great discussion.