-
Notifications
You must be signed in to change notification settings - Fork 37
/
values.yaml
249 lines (228 loc) · 8.95 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
# Default values for wicked.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.
# namespace to deploy wicked to:
namespace: default
# Set to true if RBAC is enabled inside your cluster, failing to mismatch
# this setting with your cluster will result in strange things, like pods
# not starting, and/or hanging in the init container steps (waiting for
# other containers/pods to start).
useRbac: false
# Deadline for all pods to come up successfully (in seconds)
deployDeadline: 300
# Specify true to deploy the chatbot
deployChatbot: false
# Specify true to deploy the mailer
deployMailer: false
# Deploy a Redis database for the sessions; the configuration of the
# Redis connection to the portal must be done in your static config,
# e.g. using the Kickstarter.
redis:
# Whether this Helm chart should also deploy a redis server, or if you
# want to use an external one (or none at all)
deployRedis: true
# The image for redis to use
image: "redis:5-alpine"
# Specify true to make the portal use redis as a session store. This requires
# a compatible configuration (i.e. created with wicked Kickstarter 0.12.1+)
useRedis: true
# If you don't deploy redis, but still use redis, you must specify the correct parameters here.
# If you specify to deploy redis inside your own cluster (deployRedis), these values will not be used.
host: "redis.provider.com"
port: "6379"
password: "some_password"
# Redis resources
resources:
requests:
cpu: 50m
memory: 128Mi
# If you are trying out wicked on minikube, please supply
# the `minikube ip` address here:
minikubeIP: ""
image:
# Use the Alpine images? Recommended, as they are just a fraction of the size (~60 MB
# instead of ~300MB compressed).
alpine: true
# Use "haufelexware/wicked." for the official ones, otherwise use the prefix you
# need to pull your company's version of wicked.
repository: "haufelexware/wicked."
# The docker image tag to use; usually you don't change this.
tag: "1.0.0-rc.14"
pullPolicy: IfNotPresent
# Add imagePullSecrets like this in an override.yaml to pass in with helm install
#imagePullSecrets:
#- name: your.registry.io
config:
# The default password of the user [email protected]
adminPassword: wicked
# It's not advisable to use the "default" environment; please create a dedicated
# environment for your deployment; this is for the sample repository. For new configurations,
# the Kickstarter (0.12.1+) creates a default k8s configuration called "k8s" which is intended
# for use with this Helm chart.
envName: k8s
# This is the deployment key for the sample repository; it needs to be
# overridden with your deployment key
deployKey: 2c94d4ffce4b631a776289dca18bc9afec60f667
# Override with your own git repository, as reachable from your k8s cluster.
repository: "github.com/apim-haufe-io/wicked-sample-config"
# Replace with your git (read only) credentials, "username:password", or leave empty
# if the repo is readable to the public (like the sample repo above)
credentials: ""
# Specify this (a git SHA1 revision, full length) if you want to pull a specific
# configuration version. Use either this or branch, or none to pull HEAD of master
# It's recommended to really specify a git ref here, to avoid configuration drift
# if the portal-api container (which will use this information is restarted for some
# reason).
revision: ""
# Specify a branch to pull for the APIm configuration. Use either this or revision,
# or none of both to pull HEAD of master.
branch: ""
# Node debugging filter, specifying "*" here makes the wicked components very chatty;
# use "wicked-sdk" for debugging the wicked SDK
debug: ""
# Specify the log level for the wicked components. Supports "debug", "info", "warn"
# or "error".
logLevel: "info"
# In case you bake in the configuration of wicked into a derivative of portal-api,
# specify the name of the image here. In case this is set to true, the git configuration
# will not be specified in the portal-api image.
useCustomApiImage: false
# Specify your custom portal-api image here in case the above is set to true.
customApiImage: "registry/repo/image:tag"
# All these values, except for pgSsl, have defaults set in the default environment
# configurations which match the sample deployments (points to the PG service inside
# the Kubernetes cluster). If they are not explicitly overridden with other values,
# they will not be introduced as environment variables to the wicked API container
# at all.
storage:
pgHost: ""
pgPort: ""
pgDatabase: ""
pgUser: ""
pgPassword: ""
pgSsl: false
# Tweaking the behaviour of the Postgres node.js driver.
# Number of times wicked API tries to connect to Postgres
pgConnectRetries: 30
# Delay between (failed) connection attempts
pgConnectDelay: 2000
# Maximum number of connections in the connection pool
pgMaxClients: 10
# Postgres connection timeout
pgConnectTimeout: 10000
# Postgres idle connection in connection pool timeout
pgIdleTimeout: 120000
# Standard resources for the node components of wicked.
resources:
api:
requests:
cpu: 50m
memory: 128Mi
portal:
requests:
cpu: 50m
memory: 128Mi
kongAdapter:
requests:
cpu: 50m
memory: 128Mi
chatbot:
requests:
cpu: 10m
memory: 128Mi
mailer:
requests:
cpu: 10m
memory: 128Mi
# Ingress specification
ingress:
enabled: true
# Value for ingress class, defaults to nginx
class: nginx
# Used to create Ingress record; the FQDN of the portal and API hosts. These
# must be set using an A or CNAME record by yourself.
apiHost: api.portal.com
portalHost: portal.com
# Set this value to true to add kube-lego annotations to the ingress resources.
# If you do this, make sure the above FQDNs are already set before you deploy.
useKubeLego: false
# If useKubeLego is false, set this to true to use the secret names in the tls
# property for the ingresses. Otherwise the standard secrets for "portal.com" and
# "api.portal.com" are used.
existingTls: false
# If existingTls is true, specify the secret names for the certificates here
tls:
apiHostSecret: gateway-ingress-tls
portalHostSecret: portal-ingress-tls
# Settings for the persistence of the dynamic data of the API Portal.
# This has to be a file storage somewhere; if you do not choose to persist
# data here, you will lose all user data if the wicked.portal-api container
# goes down.
persistence:
# Use a PVC to persist data
enabled: false
# Provide an existing PersistentVolumeClaim nil
existingClaim: nil
# Storage class of backing PVC (uses alpha storage class annotation)
storageClass: nil
# Use volume as ReadOnly, ReadWrite or ReadWriteOnce
accessMode: ReadWriteOnce
# Size of data volume
size: 1Gi
# Subdirectory of the volume to mount at (useful for NFS mounts with hidden files in base),
# or if containers share NFS shares.
subPath: ""
# Specify the resource for Kong here
kong:
# Number of replicas of Kong to spin up; for HA, you will want to set this to at least 2
replicas: 1
resources:
requests:
memory: 256Mi
cpu: 100m
# Specify which headers are passed to the upstream;
# See https://docs.konghq.com/0.14.x/configuration/#headers
# Specify "off" to not return any tokens.
headers: "server_tokens, latency_tokens"
# Postgres configuration
postgres:
# Deploy a Kong Postgres storage with this application? If you specify false here,
# you will need to take care of your Postgres instance yourself
deployPostgres: true
## Specify runtime config parameters as a dict, using camelCase, e.g.
## {"sharedBuffers": "500MB"}
## ref: https://www.postgresql.org/docs/current/static/runtime-config.html
runtimeConfig: {"maxConnections": "300"}
# Which Postgres version do you want to deploy? Do NOT change this when upgrading, it
# will not end well.
version: "9.6"
# In case you choose not to deploy Postgres along with Kong, you must specify the
# following values.
pgHost: postgres.host.com
pgPort: "5432"
# These values are used both to prime your local database (deployPostgres=true) or
# if you choose to run a custom postgres instance.
pgDatabase: kong
pgUser: kong
pgPassword: kong
# Set to true make PG require SSL
pgSsl: false
resources:
requests:
memory: 256Mi
cpu: 50m
# Persist Postgres storage? This is mandatory for production scenarios, in case you
# do not decide to roll your own Postgres (i.e. deployPostgres=false)
persistence:
# Use a PVC to persist data true
enabled: false
# Provide an existing PersistentVolumeClaim
existingClaim: ""
# Storage class of backing PVC (uses alpha storage class annotation)
storageClass: ""
# Use volume as ReadOnly, ReadWrite or ReadWriteOnce
accessMode: ReadWriteOnce
# Size of data volume
size: 2Gi
# Subdirectory of the volume to mount at (useful for NFS mounts with hidden files in base)
subPath: ""