-
Notifications
You must be signed in to change notification settings - Fork 3
/
values.yaml
185 lines (147 loc) · 5.76 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
image:
repository: pecan/bety
tag: null
checks: "ncsa/checks:1.0.1"
pullPolicy: IfNotPresent
imagePullSecrets: []
## replicaCount is the number of instances for BETYDB. Each instance can also
## have multuiple workers as defined by workers below.
replicaCount: 1
## workers is the number of workers for each BETYDB replica. The total number
## of simultanous connections is replicaCount * workers.
workers: 1
## localServer is the ID for this intance. To be able to synchronize your data
## with the PEcAn network you will need to request a unique number. This can
## be done at https://forms.gle/m3SnMVh8WVHyL6eH8
localServer: 99
## remoteservers is the list of all remote servers you want to synchronize with.
## This is the list you will receive data from.
remoteServers: "0, 1, 2, 5"
## betyUser is the user that is used with PostgreSQL. BETYDB and PEcAn will use
## this user to connect to the database and read and write to the database.
betyUser: bety
## betyPassword the password used when connecting to the database from BETYDB
## and PEcAn.
betyPassword: bety
## betyDatabase the database that will be created and that BETYDB adn PEcAn
## will connect to and write data.
betyDatabase: bety
## secretKey the key that will be used to encrypt the passwords. If this is
## changed users will not be able to login with their existing passwords.
secretKey: thisisnotasecret
## dbtag is the tag of the database to load. Normally will use latest to
## make sure latest tag is loaded, this might not work with an older database.
## set this to "" to not load the database
dbtag: latest
## dburl is the url where to get the database from. If this is not set use
## the dbdump that is the PEcAn network. The default is not to use this.
dburl: ""
## addUsers is a hash of users that should be added to the database when it is
## initialized.
# data : 1=Restricted, 2=Internal, 3=External, 4=Public
# page : 1=Admin, 2=Manager, 3=Creator, 4=Viewer
users: []
# - username: carya
# password: illinois
# fullname: Demo User
# email: betydb@gmail.com
# data: 1
# page: 1
# - username: guestuser
# password: guestuser
# fullname: Guest User
# email: betydb@gmail.com
# data: 4
# page: 4
# customization of BETY:
# - application will be placed in config/application.yml
# - logos will be placed in public/images/custom
customization: {}
# application: |
# organization:
# name: "TERRA Ref"
# url: #{root_path}
# logo_file: "custom/terraref-logo.png"
# logos:
# "terraref-logo.png": <base64 values>
# -------------------------------------------------------------------------------
## All data for BETYDB will be stored in PostgreSQL
postgresql:
## enabled should the postgresql chart be installed as well. If not make
## sure that the other values are provied to get access to the database.
enabled: true
## it takes some time to start postgresql, wait 5 min before start liveness.
livenessProbe:
initialDelaySeconds: 300
## postgresqlHost host where postgresql is installed.
# postgresqlHost: postgres
## postgresqlPort port to connect to postgresql
# postgresqlPort: 5432
auth:
## enablePostgresUser adds the postgres user This user will have superuser abilities.
# enablePostgresUser: true
## postgresPassword the password for postgres, if using auto generated
## password make sure to save the password as described in the notes. When upgrading
## you will need to provide this secret otherwise a new secret will be generated but
## not saved in the database.
postgresPassword: supersecret
# we will only configure the primary database
primary:
# need more space
persistence:
size: 20Gi
# -------------------------------------------------------------------------------
nameOverride: ""
fullnameOverride: ""
# -------------------------------------------------------------------------------
service:
type: ClusterIP
port: 8000
# -------------------------------------------------------------------------------
## Configure the ingress resource that allows you to access the
## BETY installation. Set up the URL
## ref: http://kubernetes.io/docs/user-guide/ingress/
##
ingress:
## Set to true to enable ingress record generation
enabled: false
## Ingress path
path: /
## The list of hostnames to be covered with this ingress record.
## Most likely this will be just one host, but in the event more hosts are needed, this is an array
hosts: []
# - bety.example.com
tls: false
# secretName: bety.example.com.tls
## Ingress annotations done as key:value pairs
##
## For a full list of possible ingress annotations, please see
## ref: https://github.com/kubernetes/ingress-nginx/blob/master/docs/annotations.md
##
annotations:
# kubernetes.io/ingress.class: nginx
# kubernetes.io/tls-acme: true
resources: {}
# We usually recommend not to specify default resources and to leave this as a conscious
# choice for the user. This also increases chances charts run on environments with little
# resources, such as Minikube. If you do want to specify resources, uncomment the following
# lines, adjust them as necessary, and remove the curly braces after 'resources:'.
# limits:
# cpu: 100m
# memory: 128Mi
# requests:
# cpu: 100m
# memory: 128Mi
## Node selector
## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#nodeselector
nodeSelector: {}
## Tolerations
## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
tolerations: []
## Affinity
## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity
affinity: {}
## Hook Affinity
## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity
hooks:
affinity: {}