stackabletech / stackabletech/trino-operator
Allow mounting extra volumes to provide files that Trino might need to authenticate against external systems
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 63
- Forks
- 13
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 12
Description
This is a similar issue to https://github.com/stackabletech/druid-operator/pull/415 and https://github.com/stackabletech/nifi-operator/pull/434.
Trino may need to authenticate to backend systems that it interacts with, for example to authenticate with a kerberized HDFS we'd need to provide krb5.conf and keytab files, or as with Druid, to access GCS volumes, a google credentials file is needed.
Since Trino has a great many possible catalogs that it can connect to and this will probably grow over time, we should probably expose something very generic here to enable it - hence mounting files.
We can at a later stage always add convenience functions that automatically provision keytabs and krbconfs for a realm that is under management by us for example.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the comparable Druid PR 415 and NiFi PR 434 linked in the issue, then locate the Trino operator's configuration for mounted volumes. Done means users can provide generic files such as krb5.conf, keytabs, or Google credentials for mounting into Trino pods.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100