-
Notifications
You must be signed in to change notification settings - Fork 1
/
values.yaml
210 lines (173 loc) · 7.05 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
# RATING-OPERATOR CHART CONFIGURATION
# DISCLAIMER: This ONLY configure the chart, not the operator itself.
# DISCLAIMER: Installing as a chart is deprecated and will be removed in the future.
# This file holds the configuration used by Helm to deploy rating-operator as a chart.
# Use only if you want to have full control over updates, default configuration, custom resources, etc.
# It is kept for compatibility but is not tested nor maintained anymore.
## The security part of the configuration is related to your cluster authentication method (cert files, token, non local users management)
security:
# The "auth" flag enables TLS/HTTPS verification in the component
# Enable it if your cluster uses HTTPS
auth: "false"
# The "adminToken" string configure the application security key
# It is used for administrator requests to the rating-operator-api and as a secret key for session encoding
token:
admin: thisisadmintoken
# The "adminAccount" variable defines the which tenant is considered admin.
# Usually, the default "admin" is enough. Some external applications already using the "admin" name could motivate to change this parameter.
# Don't forget to edit the Grafana deployment accordingly, to syncronise both adminAccount values.
adminAccount: admin
# Keycloak can be used as an authentication method through the operator.
# Setting enabled to "false" will configure the rating-operator to use its own local user management
keycloak:
enabled: "false"
## Below the configuration for the Keycloak server
# serverUrl: "my_url_keycloak"
# clientID: rating-operator
# realmName: "my_realm"
# clientSecretKey: "bakshdhb-dkjashbdjh-dkjahdfskl"
## Location of the prometheus component
prometheus:
service: prometheus-kube-prometheus-prometheus
namespace: monitoring
schema: http
domain: svc.cluster.local
port: 9090
## Configuration of the api component
api:
# Pod name
name: api
# Below lies the name of the postgresql pod running along the rating-operator-api
config:
postgres_hostname: "{{ .Release.Name }}-postgresql-headless"
postgres_secret: "{{ .Release.Name }}-postgresql"
# Image tags
# These options are mostly for developpers
# Base values should satisfy user needs
image:
pullPolicy: Always
repository: alterwayrnd/rating-operator-api
tag: master
# Resources allocation
# Leaving empty is fine, use only if you know what you are doing, as lack of resources can starve the operator
affinity: {}
nodeSelector: {}
resources: {}
tolerations: []
# rating-operator-api service configuration
# To be used to expose the api to the web
service:
port: 80
type: ClusterIP
# The rating-operator supports rook-ceph and longhorn storageClasses out of the box
# Follow the rating-operator documentation for more details about their installation and configuration.
# Different storageClass / provider could be used, but we do not warranty positive results.
storage:
storageClass: longhorn
# This value configuration where to reach the metering-operator storage system
# Do not modify if you don't have a specific need
# The usage of metering-operator is deprecated
metering:
presto_database_uri: presto://[email protected]:8080/hive/metering
# Storage pod configuration
# Uses a compressed bitnami/postgresql chart
# See https://github.com/bitnami/charts/blob/master/bitnami/postgresql/values.yaml for more options
global:
storageClass: longhorn
postgresql:
storageClass: longhorn
storageClass: longhorn
postgresql:
enabled: true
# As mentionned above, rating-operator support rook-ceph and longhorn out of the box
storageClass: longhorn
# Both password and PostgresPassword have to be set if your postgresqlUsername is "postgres"
postgresqlUsername: postgres
postgresqlPassword: notasecret
postgresqlPostgresPassword: notasecret
# Openshift/OKD specifics
# Modify only if you have trouble allocating / RBAC problems with your storage pod on Openshift
# securityContext:
# enabled: true
# fsGroup: 1000600000
# runAsUser: 1000600000
# volumePermissions:
# enabled: false
# securityContext:
# runAsUser: 1000600000
## Configuration of the manager component
manager:
# Pod name
name: manager
# Image tags
# Mostly for developpers, the base values should satisfy user needs
image:
pullPolicy: Always
repository: alterwayrnd/rating-operator-manager
tag: master
# Resources allocation
# Leaving empty is fine, use only if you know what you are doing, as lack of resources can starve the operator
affinity: {}
nodeSelector: {}
resources: {}
tolerations: []
## Configuration of the engine component
engine:
# Pod name
name: engine
# Image tags
# Mostly for developpers, the base values should satisfy user needs
image:
pullPolicy: Always
repository: alterwayrnd/rating-operator-engine
tag: master
# Resources allocation
# Leaving empty is fine, use only if you know what you are doing, as lack of resources can starve the operator
affinity: {}
nodeSelector: {}
resources: {}
tolerations: []
## Configuration of the frontend component
# Grafana is used as the base frontend for the rating-operator
frontend:
# The address to which you'll be redirected once logged in through the rating-operator
url: "localhost:3000"
# If you try to connect a different frontend to the application, this might be needed
allowOrigin: "*"
# Grafana configuration
grafana:
# Password for the administrator account
password: prom-operator
# The address toward which the requests made to Grafana will be directed
backend: "prometheus-grafana.monitoring.svc.cluster.local"
# Helpers for cookies
# Grafana session through HTTPS requires specific cookie handling
env:
domain: ""
httponly: "false"
secure: "false"
samesite: "none"
# Convenience options, usually left as default
rbac:
create: true
service:
port: 80
type: ClusterIP
nameOverride: null
networkPolicy:
enabled: false
fullnameOverride: null
ingress:
annotations: {}
enabled: false
hosts:
- host: chart-example.local
paths: []
tls: []
# Left for compatibility
api:
pullSecretsName: rating-regcred
manager:
pullSecretsName: rating-regcred
engine:
pullSecretsName: rating-regcred