-
Notifications
You must be signed in to change notification settings - Fork 12
/
Copy pathvalues.yaml
107 lines (104 loc) · 4.03 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
# Drill Image repository
repo: hub.docker.com/u/
# Global sub-section
global:
# Namespace for the Drill chart (and dependent Zookeeper chart)
# Note that only one Drill cluster can be deployed in a given namespace
namespace: default
# Drill sub-section
drill:
# Name of the Drill cluster. Also used to create the ZK node for the Drill cluster
id: drillcluster1
# Kubernetes environment. Currently supported values: [gke, on-prem]
environment: gke
# Number of Drill Pods which are launched in parallel and join to form a Drill Cluster
count: 2
# Total memory for each Drill pod
memory: 5Gi
# Total CPU for each Drill pod
cpu: 4000m
# Drill image with tag
image: agirish/drill:1.17.0
# Drill's HTTP port
httpPort: 8047
# User Server port. The Bit Server Port and Data Server ports are +1 and +2
userServerPort: 31010
# Periodically, a diagnostic is performed to check the 'liveness' of a Drill container
# The livenessProbe indicates whether the Container is running. If the probe fails, it's restarted
livenessProbe:
exec:
# The absolute path of the liveness probe script on the pod
command:
- sh
- -c
- /opt/drill/bin/isLive.sh
# Number of seconds after the container has started before probes are initiated
# (to account for time taken by Drillbit process to start)
initialDelaySeconds: 10
# Number of seconds after which to retry probes
periodSeconds: 30
# Number of seconds after which probes time out
timeoutSeconds: 10
# Number of retries in case of probe failures
failureThreshold: 10
# Periodically, a diagnostic is performed to check the 'readiness' of a Drill container
# The readinessProbe indicates whether the Container is ready to service requests. If the probe fails,
# the Pod's IP address is removed from the endpoints of all Services that match the Pod
readinessProbe:
exec:
# The absolute path of the readiness probe script on the pod
command:
- sh
- -c
- /opt/drill/bin/isReady.sh
# Number of seconds after the container has started before probes are initiated
# (to account for time taken by Drillbit process to start)
initialDelaySeconds: 10
# Number of seconds after which to retry probes
periodSeconds: 30
# Number of seconds after which probes time out
timeoutSeconds: 10
# Number of retries in case of probe failures
failureThreshold: 5
# Lifecycle hooks
lifecycle:
# During a scale down of the Drill Cluster, a preStop hook is executed on the pod replicas
# that are to be brought down, which instructs the Drillbit process to gracefully shutdown
preStop:
exec:
# The absolute path of the preStop script on the pod
command:
- sh
- -c
- /opt/drill/bin/preStop.sh
# Number of seconds after which pods are forcefully killed
# Note: Lower values may cause running queries to fail
terminationGracePeriodSeconds: 60
# Drill Configuration can be overridden by mounting them on each Drill container.
# Edit the files in `conf` with your custom configurations
# Use `conf/createCM.sh` to create the ConfigMap
drillConf:
# Flag to turn-on / turn-off this option
override: false
# Name of the ConfigMap with Drill config files
configMapName: drill-config-override-cm
# The size of the Drill cluster (number of Drill Pod replicas) can be autoscaled
# With higher CPU utilization, more drill-bits are added automatically. And as the load goes down,
# so do the number of drill-bits in the Drill Cluster (by gracefully shutting down)
autoscale:
# Flag to turn-on / turn-off this option
enabled: false
# Maximum number of Drill Pods
maxCount: 4
# Target CPU Utilization Percentage
cpuThreshold: 75
# ZooKeeper sub-section
zookeeper:
# Name of the ZooKeeper quorum (currently single-node configuration only)
id: zk
# Total memory for each ZooKeeper pod
memory: 2Gi
# Total CPU for each ZooKeeper pod
cpu: 500m
# ZooKeeper image with tag
image: agirish/zookeeper:3.6.0