-
Notifications
You must be signed in to change notification settings - Fork 20
/
values.yaml
116 lines (98 loc) · 4.32 KB
/
values.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
presto:
# environment is the name given to the presto environment within all presto nodes
# (containers). This value can be used to more easily distinguish colocated
# installations. This value isn't as useful in kubernetes where installs are
# already distinguished by kubernetes and helm. The most useful place for this
# is in the presto web UI to identify the installation.
environment: "production"
# workers specifies the number of worker nodes (containers) to launch during
# installation. This can be scaled later if desired.
workers: 2
# logLevel is the logging level for the presto service on each node. Should be
# one of "DEBUG", "INFO", "WARN", or "ERROR".
logLevel: "INFO"
image:
# repository is the name of the docker image that will be used in the Presto
# coordinator and worker deployments.
repository: "wiwdata/presto"
# tag of the docker image that will be used by the coordinator and worker
# deployments.
tag: "0.217"
# pullPolicy specifies the image pull policy for both the worker and
# coordinator deployment containers.
pullPolicy: "Always"
# containerSpec allows for adding arbitrary yaml to the spec under which the
# coordinator and worker definitions reside. This can be useful in cases where
# private registry credentials are necessary pulling images.
containerSpec: {}
service:
type: ClusterIP
# catalog defines the connectors available within the presto environment.
# Specify each value as a NAME.properties key and the values as the desired
# contents of that catalog file. These will be loaded into the image as the
# connector files. Prior to loading them in as connectors, they will be
# rendered by Jinja2 using any supplied environment variables in the container
# that begin with the prefixes USER_ or SECRET_. This can be used to
# include secrets in catalog files at runtime using standard kubernetes
# secret mapping techniques.
catalog: {}
# hive.properties: |
# connector.name=hive-hadoop2
# hive.metastore-cache-ttl=20m
# hive.non-managed-table-writes-enabled=false
# hive.s3-file-system-type=PRESTO
# hive.hdfs.impersonation.enabled=true
# hive.metastore=glue
# coordinatorConfigs are configuration file values applied to the coordinator
# container. Required and recommended defaults will be applied where any of
# these are missing. For more details on files and options see:
# https://prestodb.github.io/docs/current/installation/deployment.html
#
# If a jvm.config is specified here it will fully override the default
# jvm.config bcause unlike the other properties independent settings are
# not necessarily compatible and could lead to unstable behavior.
#
# These values are rendered with Jinja2 just like the catalog values above
# to allow for greater flexibility in runtime configuration.
coordinatorConfigs: {}
# config.properties: |
# http-server.log.max-size=10MB
# http-server.log.max-history=5
# workerConfigs are configuration file values applied to the worker containers.
# This has the same behaviors as the coordinatorConfigs defined above.
workerConfigs: {}
# Additional environment variables to include in the containers.
environmentVariables:
# - name: SECRET_USERNAME
# valueFrom:
# secretKeyRef:
# name: test-secret
# key: username
coordinatorResources: {}
# We usually recommend not to specify default resources and to leave this as a conscious
# choice for the user. This also increases chances charts run on environments with little
# resources, such as Minikube. If you do want to specify resources, uncomment the following
# lines, adjust them as necessary, and remove the curly braces after 'resources:'.
# limits:
# cpu: 100m
# memory: 128Mi
# requests:
# cpu: 100m
# memory: 128Mi
workerResources: {}
# We usually recommend not to specify default resources and to leave this as a conscious
# choice for the user. This also increases chances charts run on environments with little
# resources, such as Minikube. If you do want to specify resources, uncomment the following
# lines, adjust them as necessary, and remove the curly braces after 'resources:'.
# limits:
# cpu: 100m
# memory: 128Mi
# requests:
# cpu: 100m
# memory: 128Mi
coordinatorNodeSelector: {}
workerNodeSelector: {}
coordinatorTolerations: []
workerTolerations: {}
coordinatorAffinity: {}
workerAffinity: {}