-
Notifications
You must be signed in to change notification settings - Fork 69
/
Copy pathvalues.yaml
119 lines (100 loc) · 3.54 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
prefectVersionTag: 2.0b7-python3.8
api:
enabled: true
service:
type: ClusterIP
port: 4200
replicaCount: 1
image:
name: prefecthq/prefect
pullPolicy: IfNotPresent
# -- Overrides the image tag whose default is the chart appVersion.
tag: 2.0b7-python3.8
debug_enabled: false
autoscaling:
# -- Enable autoscaling
enabled: false
# -- Minimum autoscaling replica count
minReplicas: 1
maxReplicas: 100
targetCPUUtilizationPercentage: 80
# targetMemoryUtilizationPercentage: 80
# -- Ingress configuration
ingress:
enabled: false
className: ""
annotations: {}
hosts:
- host: prefect.local
paths:
- path: /
pathType: ImplementationSpecific
tls: []
nodeSelector: {}
tolerations: []
affinity: {}
podAnnotations: {}
podSecurityContext: {}
securityContext: {}
resources: {}
postgresql:
auth:
database: orion
# postgresqlUsername defines the username to authenticate
# with.
# NOTE: If you are using Azure, this will include an '@'
# which must be encoded as '%40' for the connection string
# to work with both Hasura, the GraphQL server, and the
# Alembic migration manager
username: prefect
# password sets the password to be used if
# `existingSecret` is not set. This is the password for
# `username` and will be set within the secret at
# the key `postgresql-password`. This argument is only relevant
# when using the Postgres database included in the chart.
# For an external postgres connection, you must create
# and use `existingSecret` instead of `postgresqlPassword`.
password: "HEREWEGO"
# existingSecret configures which secret should be referenced
# for access to the database. If null and `useSubChart` is
# enabled, the secret will be generated. If using an external
# postgres service, this value should be set to the name of
# an existing Kubernetes secret. This secret must contain
# a key-value pair where the key is `postgresql-password `
# and the value is your password. For more information,
# see the "Database" section of the README.
existingSecret: null
# servicePort configures the port that the database should be
# accessed at
containerPorts:
postgresql: 5432
# externalHostname defines the address to contact an externally
# managed postgres database instance at. This is not required if
# `internalPostgres` is `true`
externalHostname: ""
# useSubChart determines if a this chart should deploy a
# user-manager postgres database or use an externally managed
# postgres instance. If `useSubChart` is `true`, the
# bitnami/postgresql subchart will be deployed
useSubChart: true
# postgresql configuration below here is only used if using
# the subchart
# persistence enables a PVC that stores the database between
# deployments. If making changes to the database deployment, this
# PVC will need to be deleted for database changes to take effect.
# This is especially notable when the authentication password
# changes on redeploys.
# This is disabled by default because we do not recommend using
# the subchart deployment for production deployments.
persistence:
# -- Enables a PVC that stores db between deployments
enabled: false
# -- Configures size of postgres PVC
size: 8Gi
# -- initial postgres user to create
initdbUser: postgres
image:
# -- Version tag, corresponds to tags at https://hub.docker.com/r/bitnami/postgresql/
tag: 14.3.0
serviceAccount:
enabled: true