charts
charts copied to clipboard
trinodb
Hi all! Thanks for a great chart, but it lacks some functionality. In our environment we needed to use a ldap auth, so i've added this to a chart, and...
Switch workerExtraConfig indentation to 2 Switch coordinatorExtraConfig indentation to 2 Before config.properties: | coordinator=true node-scheduler.include-coordinator=false http-server.http.port=8080 query.max-memory=4GB query.max-memory-per-node=1GB discovery.uri=http://localhost:8080 someKey=someValue After config.properties: | coordinator=true node-scheduler.include-coordinator=false http-server.http.port=8080 query.max-memory=4GB query.max-memory-per-node=1GB discovery.uri=http://localhost:8080 someKey=someValue
The initContainers is located in the middle of the volume declarations. As a fix, it can be relocated out of the declarations.
This to provide ability to use our own configmap for the catalogs instead of adding the catalogs inline in the values.yaml, for example : catalogsConfigmapOverride: my-trino-catalog-configmap Thanks.
This will be useful when we want to add different line in node.properties for coordinator and workers, for example : server: coordinatorExtraNodeConfig: | node.id=trino-coordinator-XcaXd workerExtraNodeConfig: | node.id=${ENV:HOSTNAME} Thanks.
The issue with password authentication working only when it is set as the only authentication type has been fixed. Since now in the templates it checks for a substring instead...
Hello, This PR is made for give ability to set custom parameter inside access-control.properties file It's needed to be compatible with a custom system access control implementation : https://trino.io/docs/current/develop/system-access-control.html I'm...
This is useful because in our clusters we use pod labels to manipulate and organize how things are moved/shifter or even how they can access the network on a pod-level...
Currently, init container config position of coordinator pod template is not valid. (between secret volumes)
