Scribd
Upload
38 views8 pages

Trino - Customized

This document outlines the steps for deploying Trino using Helm with a customized values.yaml file, including pulling the Trino chart, modifying the configuration, and setting the service type to ClusterIP. It provides specific commands for setting up the repository, altering the catalog configuration, and deploying the service in a Kubernetes namespace. Additionally, it includes instructions for pushing the deployment to a Git repository for version control.

Uploaded by

saranya.p
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
38 views8 pages

Trino - Customized

This document outlines the steps for deploying Trino using Helm with a customized values.yaml file, including pulling the Trino chart, modifying the configuration, and setting the service type to ClusterIP. It provides specific commands for setting up the repository, altering the catalog configuration, and deploying the service in a Kubernetes namespace. Additionally, it includes instructions for pushing the deployment to a Git repository for version control.

Uploaded by

saranya.p
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

Trino -

Open SCM
a) Pull a Trino chart
b) Upload it in a Repo
c) Alter the Templates -> Catalog config map
d) Let the Service be Cluster IP

Trino deployment using customized values.yaml file:


a)
→ helm repo add trino https://trinodb.github.io/charts
→ helm repo update
→ helm pull trino/trino --untar
→ ls

→ cd trino/
→ ls

→ cd templates/
→ ls

→ Remove other yaml files that aren’t needed like ingress.yaml, networkpolicy.yaml,.

c) d)
→ values.yaml
nameOverride:
coordinatorNameOverride:
workerNameOverride:
image:
registry: ""
repository: trinodb/trino
tag: ""
digest: ""
useRepositoryAsSoleImageReference: false
pullPolicy: IfNotPresent
imagePullSecrets: []
server:
workers: 2
node:
environment: production
dataDir: /data/trino
pluginDir: /usr/lib/trino/plugin
log:
trino:
level: INFO
config:
path: /etc/trino
https:
enabled: false
port: 8443
keystore:
path: ""
authenticationType: ""
query:
maxMemory: "4GB"
exchangeManager: {}
workerExtraConfig: ""
coordinatorExtraConfig: ""
autoscaling:
enabled: false
maxReplicas: 5
targetCPUUtilizationPercentage: 50
targetMemoryUtilizationPercentage: 80
behavior: {}
accessControl: {}
resourceGroups: {}
additionalNodeProperties: []
additionalConfigProperties: []
additionalLogProperties: []
additionalExchangeManagerProperties: []
eventListenerProperties: []
catalogs:
hive: |
connector.name=hive
hive.metastore.uri=thrift://hive-metastore:9083
mysql: |
connector.name=mysql
connection-url=jdbc:mysql://mysql-host:3306
additionalCatalogs: {}
env: []
envFrom: []
initContainers: {}
sidecarContainers: {}
securityContext:
runAsUser: 1000
runAsGroup: 1000
containerSecurityContext:
allowPrivilegeEscalation: false
capabilities:
drop:
- ALL
shareProcessNamespace:
coordinator: false
worker: false
service:
annotations: {}
type: ClusterIP
port: 8080
auth: {}
serviceAccount:
create: false
name: ""
annotations: {}
configMounts: []
secretMounts: []
coordinator:
deployment:
annotations: {}
progressDeadlineSeconds: 600
revisionHistoryLimit: 10
strategy:
type: RollingUpdate
rollingUpdate:
maxSurge: 25%
maxUnavailable: 25%
jvm:
maxHeapSize: "8G"
gcMethod:
type: "UseG1GC"
g1:
heapRegionSize: "32M"
config:
memory:
heapHeadroomPerNode: ""
query:
maxMemoryPerNode: "1GB"
additionalJVMConfig: []
additionalExposedPorts: {}
resources: {}
livenessProbe: {}
readinessProbe: {}
lifecycle: {}
terminationGracePeriodSeconds: 30
nodeSelector: {}
tolerations: []
affinity: {}
additionalConfigFiles: {}
additionalVolumes: []
additionalVolumeMounts: []
annotations: {}
labels: {}
configMounts: []
secretMounts: []
worker:
deployment:
annotations: {}
progressDeadlineSeconds: 600
revisionHistoryLimit: 10
strategy:
type: RollingUpdate
rollingUpdate:
maxSurge: 25%
maxUnavailable: 25%
jvm:
maxHeapSize: "8G"
gcMethod:
type: "UseG1GC"
g1:
heapRegionSize: "32M"
config:
memory:
heapHeadroomPerNode: ""
query:
maxMemoryPerNode: "1GB"
additionalJVMConfig: []
additionalExposedPorts: {}
resources: {}
livenessProbe: {}
readinessProbe: {}
lifecycle: {}
gracefulShutdown:
enabled: false
gracePeriodSeconds: 120
terminationGracePeriodSeconds: 30
nodeSelector: {}
tolerations: []
affinity: {}
additionalConfigFiles: {}
additionalVolumes: []
additionalVolumeMounts: []
annotations: {}
labels: {}
configMounts: []
secretMounts: []
kafka:
mountPath: "/etc/trino/schemas"
tableDescriptions: {}

→ Altered configMap-catalog in values.yaml file;


catalogs:
hive: |
connector.name=hive
hive.metastore.uri=thrift://hive-metastore:9083
mysql: |
connector.name=mysql
connection-url=jdbc:mysql://mysql-host:3306
additionalCatalogs: {}
→ Service - Cluster IP
service:
annotations: {}
type: ClusterIP
port: 8080
→ kubectl create ns trino
→ helm install trino trino/trino -f values.yaml --namespace trino
[ trino - release name ]

→ helm upgrade trino trino/trino -f values.yaml --namespace trino (Incase of updates


with values.yaml file upgrade the already installed release - trino)

→ kubectl get all -n trino

→ kubectl get pods -n trino –watch


→ After the pods are running successfully, port-forward to access the deployed trino in
port 8080

→ localhost:8080
b)
→ git init
→ git add .
→ git commit -m “Trino”
→ git remote add origin https://github.com/saranya-232004/trino-helm.git
→ git push -u origin main

You might also like