forked from wso2/kubernetes-ei
-
Notifications
You must be signed in to change notification settings - Fork 0
/
values.yaml
274 lines (272 loc) · 13.1 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
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
# Copyright (c) 2019, WSO2 Inc. (http://www.wso2.org) All Rights Reserved.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
wso2:
# MySQL datasource configurations
# enabled: The configuration should be set to be 'true' if a MySQL database should be spawned as a pod within the cluster
# host: Hostname of the MySQL database
# username: MySQL database username
# password: MySQL database password
# driverClass: JDBC Driver class name
# validationQuery: SQL validation query
mysql:
enabled: true
host: wso2ei-rdbms-service-mysql
username: wso2carbon
password: wso2carbon
driverClass: com.mysql.jdbc.Driver
validationQuery: "SELECT 1"
# WSO2 subscription parameters. If you do not have an active subscription, do not provide values for the parameters.
# If you do not possess an active WSO2 subscription already, you can sign up for a WSO2 Free Trial Subscription at (https://wso2.com/free-trial-subscription).
subscription:
username: ""
password: ""
deployment:
wso2ei:
imageName: "wso2ei-integrator"
imageTag: "6.6.0"
# Number of deployment replicas
replicas: 1
# Minimum number of seconds for which a newly created pod should be ready without any of its containers crashing, for it to be considered available.
minReadySeconds: 75
strategy:
rollingUpdate:
# The maximum number of pods that can be scheduled above the desired number of pods.
maxSurge: 1
# The maximum number of pods that can be unavailable during the update.
maxUnavailable: 0
# Indicates whether the container is running.
livenessProbe:
# Number of seconds after the container has started before liveness probes are initiated.
initialDelaySeconds: 40
# How often (in seconds) to perform the probe.
periodSeconds: 10
# Indicates whether the container is ready to service requests.
readinessProbe:
# Number of seconds after the container has started before readiness probes are initiated.
initialDelaySeconds: 40
# How often (in seconds) to perform the probe.
periodSeconds: 10
imagePullPolicy: Always
resources:
# These are the minimum resource recommendations for running WSO2 Enterprise Integrator server profiles
# as per official documentation (https://docs.wso2.com/display/EI650/Installation+Prerequisites).
requests:
# The minimum amount of memory that should be allocated for a Pod
memory: "1Gi"
# The minimum amount of CPU that should be allocated for a Pod
cpu: "1000m"
limits:
# The maximum amount of memory that should be allocated for a Pod
memory: "2Gi"
# The maximum amount of CPU that should be allocated for a Pod
cpu: "2000m"
wso2eiBroker:
imageName: "wso2ei-broker"
imageTag: "6.6.0"
# Number of deployment replicas
replicas: 1
# Minimum number of seconds for which a newly created pod should be ready without any of its containers crashing, for it to be considered available.
minReadySeconds: 75
strategy:
rollingUpdate:
# The maximum number of pods that can be scheduled above the desired number of pods.
maxSurge: 1
# The maximum number of pods that can be unavailable during the update.
maxUnavailable: 0
# Indicates whether the container is running.
livenessProbe:
# Number of seconds after the container has started before liveness probes are initiated.
initialDelaySeconds: 40
# How often (in seconds) to perform the probe.
periodSeconds: 10
# Indicates whether the container is ready to service requests.
readinessProbe:
# Number of seconds after the container has started before readiness probes are initiated.
initialDelaySeconds: 40
# How often (in seconds) to perform the probe.
periodSeconds: 10
imagePullPolicy: Always
resources:
# These are the minimum resource recommendations for running WSO2 Enterprise Integrator server profiles
# as per official documentation (https://docs.wso2.com/display/EI650/Installation+Prerequisites).
requests:
# The minimum amount of memory that should be allocated for a Pod
memory: "1Gi"
# The minimum amount of CPU that should be allocated for a Pod
cpu: "1000m"
limits:
# The maximum amount of memory that should be allocated for a Pod
memory: "2Gi"
# The maximum amount of CPU that should be allocated for a Pod
cpu: "2000m"
wso2eiAnalyticsWorker1:
imageName: "wso2ei-analytics-worker"
imageTag: "6.6.0"
# Number of deployment replicas
replicas: 1
# Minimum number of seconds for which a newly created pod should be ready without any of its containers crashing, for it to be considered available.
minReadySeconds: 30
strategy:
rollingUpdate:
# The maximum number of pods that can be scheduled above the desired number of pods.
maxSurge: 1
# The maximum number of pods that can be unavailable during the update.
maxUnavailable: 0
# Indicates whether the container is running.
livenessProbe:
# Number of seconds after the container has started before liveness probes are initiated.
initialDelaySeconds: 20
# How often (in seconds) to perform the probe.
periodSeconds: 10
# Indicates whether the container is ready to service requests.
readinessProbe:
# Number of seconds after the container has started before readiness probes are initiated.
initialDelaySeconds: 20
# How often (in seconds) to perform the probe.
periodSeconds: 10
# Refer to the Kubernetes documentation on updating images (https://kubernetes.io/docs/concepts/containers/images/#updating-images)
imagePullPolicy: Always
resources:
# These are the minimum resource recommendations for running WSO2 Stream Processor based server profiles
# as per official documentation (https://docs.wso2.com/display/SP440/Installation+Prerequisites).
requests:
# The minimum amount of memory that should be allocated for a Pod
memory: "4Gi"
# The minimum amount of CPU that should be allocated for a Pod
cpu: "2000m"
# Please see the official documentation on WSO2 Stream Processor based Performance Analysis and Resource recommendations
# (https://docs.wso2.com/display/SP440/Performance+Analysis+Results) and tune the limits according to your needs
# where necessary.
limits:
# The maximum amount of memory that should be allocated for a Pod
memory: "4Gi"
# The maximum amount of CPU that should be allocated for a Pod
cpu: "2000m"
wso2eiAnalyticsWorker2:
imageName: "wso2ei-analytics-worker"
imageTag: "6.6.0"
# Number of deployment replicas
replicas: 1
# Minimum number of seconds for which a newly created pod should be ready without any of its containers crashing, for it to be considered available.
minReadySeconds: 30
strategy:
rollingUpdate:
# The maximum number of pods that can be scheduled above the desired number of pods.
maxSurge: 1
# The maximum number of pods that can be unavailable during the update.
maxUnavailable: 0
# Indicates whether the container is running.
livenessProbe:
# Number of seconds after the container has started before liveness probes are initiated.
initialDelaySeconds: 20
# How often (in seconds) to perform the probe.
periodSeconds: 10
# Indicates whether the container is ready to service requests.
readinessProbe:
# Number of seconds after the container has started before readiness probes are initiated.
initialDelaySeconds: 20
# How often (in seconds) to perform the probe.
periodSeconds: 10
# Refer to the Kubernetes documentation on updating images (https://kubernetes.io/docs/concepts/containers/images/#updating-images)
imagePullPolicy: Always
resources:
# These are the minimum resource recommendations for running WSO2 Stream Processor based server profiles
# as per official documentation (https://docs.wso2.com/display/SP440/Installation+Prerequisites).
requests:
# The minimum amount of memory that should be allocated for a Pod
memory: "4Gi"
# The minimum amount of CPU that should be allocated for a Pod
cpu: "2000m"
# Please see the official documentation on WSO2 Stream Processor based Performance Analysis and Resource recommendations
# (https://docs.wso2.com/display/SP440/Performance+Analysis+Results) and tune the limits according to your needs
# where necessary.
limits:
# The maximum amount of memory that should be allocated for a Pod
memory: "4Gi"
# The maximum amount of CPU that should be allocated for a Pod
cpu: "2000m"
wso2eiAnalyticsDashboard:
imageName: "wso2ei-analytics-dashboard"
imageTag: "6.6.0"
# Number of deployment replicas
replicas: 1
# Minimum number of seconds for which a newly created pod should be ready without any of its containers crashing, for it to be considered available.
minReadySeconds: 30
strategy:
rollingUpdate:
# The maximum number of pods that can be scheduled above the desired number of pods.
maxSurge: 1
# The maximum number of pods that can be unavailable during the update.
maxUnavailable: 0
# Indicates whether the container is running.
livenessProbe:
# Number of seconds after the container has started before liveness probes are initiated.
initialDelaySeconds: 20
# How often (in seconds) to perform the probe.
periodSeconds: 10
readinessProbe:
# Number of seconds after the container has started before readiness probes are initiated.
initialDelaySeconds: 20
# How often (in seconds) to perform the probe.
periodSeconds: 10
resources:
# These are the minimum resource recommendations for running WSO2 Stream Processor based server profiles
# as per official documentation (https://docs.wso2.com/display/SP440/Installation+Prerequisites).
requests:
# The minimum amount of memory that should be allocated for a Pod
memory: "4Gi"
# The minimum amount of CPU that should be allocated for a Pod
cpu: "2000m"
# Please see the official documentation on WSO2 Stream Processor based Performance Analysis and Resource recommendations
# (https://docs.wso2.com/display/SP440/Performance+Analysis+Results) and tune the limits according to your needs
# where necessary.
limits:
# The minimum amount of memory that should be allocated for a Pod
memory: "4Gi"
# The minimum amount of CPU that should be allocated for a Pod
cpu: "2000m"
# Refer to the Kubernetes documentation on updating images (https://kubernetes.io/docs/concepts/containers/images/#updating-images)
imagePullPolicy: Always
# Configurations for the logstash container image and elasticsearch authorization credentials
# Centralized logging is disabled by default. If it is required to enable centralized logging, please follow the instructions
# provided in the documentation (https://github.com/wso2/kubernetes-ei/tree/master/advanced/helm/ei-pattern-2#enabling-centralized-logging)
centralizedLogging:
enabled: false
logstash:
imageTag: 7.2.0
elasticsearch:
host: wso2-elasticsearch-master
username: "elastic"
password: "changeme"
readinessProbe:
initialDelaySeconds: 90
periodSeconds: 30
livenessProbe:
initialDelaySeconds: 90
periodSeconds: 30
monitoring:
# Enable Prometheus monitoring. This will start Prometheus exporter on port 2222 and deploy Service monitors
# for JVM, JMX and Blackbox exporter for Login calls
enabled: false
prometheus:
serviceMonitor:
# If the black box exporter is deployed in a different Namespace
# blackBoxNamespace:
# Prometheus Operator labels to identify Service monitors
labels:
release: monitoring
# Job name of the JMX events
jmxJobName: "jmx"
kubernetes:
svcaccount: "wso2svc-account"