charts
charts copied to clipboard
trinodb
Add configmap checksum for automatically roll deployments on coordinator and worker: - `depolyment-coordinator` : `configmap-catalog.yaml` & `configmap-coordinator.yaml` - `deployment-worker` : `configmap-worker.yaml`
Currently it is not possible to easily use `dynamic` catalog management because `ConfigMaps` are mounted as ReadOnly into the coordinator Pod. It would be nice having a way to work...
Give the ability to add extraVolumes and extraVolumeMounts. Typically, on a cluster with nonRoot pods strategy (OpenShift), we have to change the dataDir, because it's owned by root (the random...
Good afternoon Is it possible to transfer sensitive data from configmap to secret kubernetes? For example: Database connection data
Trino supports multiple authentication types: https://trino.io/docs/current/security/authentication-types.html#multiple-authentication-types Current chart oriented for single-valued auth type.
While trying to follow the [official instructions for TLS/HTTPS](https://trino.io/docs/current/security/tls.html#secure-trino-directly), I realised that a lot of the required flags in `config.properties` for the coordinator were not yet implemented. This PR attempts...
We want to specify `pod.spec.containers.securityContext` so I'm glad if this is supported: e.g. Superset supports that: https://github.com/apache/superset/blob/8c32c6da169afec312923e516850d90a69e78f46/helm/superset/values.yaml#L336
Allows the user to set SecuritContext configurations on container level such as allowPrivilegeEscalation: false
When trino needs to access multiple clusters, the hosts for external cluster interactions need to be added to the /etc/hosts file, otherwise the IP of domain name format may not...
With current chart, if we add ``` server: coordinatorExtraConfig: "query.client.timeout=5m" ``` then `config.properties` in coordinator configMap turns out with config extra indented: ``` coordinator=true node-scheduler.include-coordinator=false http-server.http.port=8080 query.max-memory=2GB query.max-memory-per-node=1GB memory.heap-headroom-per-node=1GB discovery-server.enabled=true...
