-
Notifications
You must be signed in to change notification settings - Fork 12
/
values.yaml
179 lines (153 loc) · 5.13 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
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
---
# The namespace for Stardog resources that override the release namespace
# namespaceOverride: stardog
# The number of Stardog replicas to deploy in the cluster
replicaCount: 3
# How to start the pods - use OrderedReady to use the default behavior of
# starting each pod one at a time or use Parallel to start them all at once
podManagementPolicy: Parallel
# The number of seconds the post install job will wait for Stardog to
# start. This includes the total time to launch the cluster in k8s,
# including ZooKeeper. Consider increasing it for k8s providers that
# have slower resource provisioning.
waitForStartSeconds: 300
cluster:
# Start Stardog as a cluster
enabled: true
# The number of seconds to wait for pods to shutdown before
# killing them forcefully
terminationGracePeriodSeconds: 300
# Java args for Stardog server
javaArgs: "-Xmx2g -Xms2g -XX:MaxDirectMemorySize=1g"
# Additional arguments passed to Stardog at server start
serverStartArgs: ""
# Stardog Java perf args, e.g. for changing Java gc
stardogPerfJavaArgs: "-XX:SoftRefLRUPolicyMSPerMB=1 -XX:+UseG1GC -XX:+UseCompressedOops"
# The service type to use for Stardog ports
service:
type: LoadBalancer
annotations: {}
# loadBalancerIP: 0.0.0.0
# The server port is the port to expose the Stardog server
# The sql port is the port to expose Stardog's business intelligence server
ports:
server: 5820
# sql: 5806
# The location Stardog will use for temporary space (i.e. java.io.tmpdir).
# If you choose to place this in STARDOG_HOME (/var/opt/stardog) for performance
# reasons, ensure that it does not conflict with any possible database names.
# For example, a good choice might be /var/opt/stardog/tmp-4646E7B662A7.
# If the directory does not exist it will be created.
tmpDir: /tmp
# The initial password for the Stardog admin user
admin:
password: admin
# passwordSecretRef: password-secret
image:
registry: https://registry.hub.docker.com/v2/repositories
repository: stardog/stardog
# Alternative config to pull from Stardog private repository
# registry: stardog-eps-docker.jfrog.io
# repository: stardog-eps-docker.jfrog.io/stardog
tag: latest
pullPolicy: IfNotPresent
# username:
# password:
# The storage class and size to use for Stardog home volumes for the pods
persistence:
storageClass: standard
size: 5Gi
nodeSelector: {}
tolerations: []
# - key: key1
# value: value1
# effect: NoSchedule
antiAffinity: requiredDuringSchedulingIgnoredDuringExecution
# Stardog should have at least 2 CPUs. The CPU request value is used to set
# -XX:ActiveProcessorCount=N for the JVM.
resources:
requests:
cpu: 2
memory: 4Gi
# limits:
# cpu: 2
# memory: 6Gi
# these allow you to configure the UID and group ID used by the container when it's running, and the fsGroup sets the group id for the volume-mounts
# if enabled: false, then the whole block is skipped
securityContext:
enabled: false
runAsUser: null
runAsGroup: null
fsGroup: null
log4jConfig:
override: false
# we provide a default log4j2.xml, if you want to provide your own. in your own values.yaml, set log4Config.override: true, and log4Config.content
# content: null
# Stardog startup probe settings. This gives the database 6 hours to start,
# e.g. if it needs to rebuild its index if necessary.
startupProbe:
periodSeconds: 30
timeoutSeconds: 15
failureThreshold: 720
# Stardog liveness probe settings. It is not generally required to modify periodSeconds and timeoutSeconds.
livenessProbe:
periodSeconds: 30
timeoutSeconds: 15
# Stardog readiness probe settings. Consider increasing initialDelaySeconds when using nodes with
# K8S nodes with limited CPUs. It is not generally required to modify periodSeconds and timeoutSeconds.
readinessProbe:
initialDelaySeconds: 15
periodSeconds: 5
timeoutSeconds: 3
# Add additional settings to the stardog config file. e.g.
# additionalStardogProperties: |
# logging.slow_query.enabled=true
# logging.slow_query.time=10s
additionalStardogProperties: |
# The busybox image is used as light weight init container as a part of
# stardog initialization.
busybox:
image:
registry: https://registry.hub.docker.com/v2/repositories
repository: busybox
tag: stable
pullPolicy: IfNotPresent
# username:
# password:
# Settings to use for the ZooKeeper chart that Stardog depends on.
# The full set of options can be found on the bitname ZK chart:
# https://github.com/bitnami/charts/tree/master/bitnami/zookeeper
zookeeper:
enabled: true
replicaCount: 3
podDisruptionBudget:
maxUnavailable: 1
persistence:
enabled: true
storageClass: standard
size: 5Gi
resources:
requests:
memory: 2Gi
cpu: 1
image:
repository: bitnami/zookeeper
tag: 3.7.1-debian-11-r58
pullPolicy: IfNotPresent
logLevel: INFO
# livenessProbe:
# enabled: true
# initialDelaySeconds: 30
# periodSeconds: 10
# timeoutSeconds: 5
# failureThreshold: 6
# successThreshold: 1
# probeCommandTimeout: 2
# readinessProbe:
# enabled: true
# initialDelaySeconds: 5
# periodSeconds: 10
# timeoutSeconds: 5
# failureThreshold: 6
# successThreshold: 1
# probeCommandTimeout: 2