forked from m-yosefpor/helm-charts
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathvalues.yaml
209 lines (185 loc) · 6.13 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
# Default values for cloud-pricing-api.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.
# -- Use the [Infracost CLI](https://github.com/infracost/infracost/blob/master/README.md#quick-start) `infracost register` command to get an API key so your self-hosted Cloud Pricing API can download the latest pricing data from us.
infracostAPIKey: ""
image:
# -- Cloud Pricing API image
repository: infracost/cloud-pricing-api
# -- Image pull policy
# pullPolicy: IfNotPresent
pullPolicy: Always
# -- Overrides the image tag whose default is the chart appVersion.
tag: ""
# -- Any image pull secrets
imagePullSecrets: []
# -- Name override for the deployed app
nameOverride: ""
# -- Full name override for the deployed app
fullnameOverride: ""
serviceAccount:
# -- Specifies whether a service account should be created
create: true
# -- Annotations to add to the service account
annotations: {}
# -- The name of the service account to use.
# If not set and create is true, a name is generated using the fullname template
name: ""
# -- Any pod annotations
podAnnotations: {}
# -- The pod security context
podSecurityContext:
{}
# fsGroup: 2000
# -- The container security context
securityContext:
{}
# capabilities:
# drop:
# - ALL
# readOnlyRootFilesystem: true
# runAsNonRoot: true
# runAsUser: 1000
service:
# -- Kubernetes service type
type: ClusterIP
# -- Kubernetes service port
port: 80
ingress:
# -- Enable the ingress controller resource
enabled: false
# -- Ingress annotation
annotations:
{}
# kubernetes.io/ingress.class: nginx
# kubernetes.io/tls-acme: "true"
# extraPaths:
# - path: /*
# backend:
# serviceName: ssl-redirect
# servicePort: use-annotation
hosts:
- # -- Host name
host: cloud-pricing-api.local
paths:
- # -- Path for host
path: /
# -- TLS configuration
tls: []
# - secretName: cloud-pricing-api-tls
# hosts:
# - cloud-pricing-api.local
postgresql:
# -- Deploy PostgreSQL servers. See [below](#postgresql) for more details
enabled: true
# -- Use an existing secret with the PostgreSQL password
existingSecret: ""
# -- Have the secrets mounted as a file instead of env vars
usePasswordFile: false
# -- Name of the PostgreSQL database
postgresqlDatabase: cloudpricingapi
# -- Name of the PostgreSQL user
postgresqlUsername: cloudpricingapi
# -- Details of external PostgreSQL server, such as AWS RDS, to use (assuming you've set postgresql.enabled to false)
external: {}
# host:
# port:
# database:
# user:
# password:
api:
# -- A 32 character API token that your Infracost CLI users will use to authenticate when calling your self-hosted Cloud Pricing API. If left empty, the helm chat will generate one for you.
# -- If you ever need to rotate the API key, you can simply update `self-hosted-infracost-api-key` in the `cloud-pricing-api` secret and restart the application.
selfHostedInfracostAPIKey: ""
# -- Set this to true to opt-out of telemetry
disableTelemetry: false
# -- Set this to debug, info, warn or error
logLevel: info
# -- Replica count
replicaCount: 1
livenessProbe:
# -- Enable the liveness probe
enabled: true
# -- The liveness probe initial delay seconds
initialDelaySeconds: 5
# -- The liveness probe period seconds
periodSeconds: 5
# -- The liveness probe timeout seconds
timeoutSeconds: 2
# -- The liveness probe failure threshold
failureThreshold: 3
# -- The liveness probe success threshold
successThreshold: 1
readinessProbe:
# -- Enable the readiness probe
enabled: true
# -- The readiness probe initial delay seconds
initialDelaySeconds: 5
# -- The readiness probe period seconds
periodSeconds: 5
# -- The readiness probe timeout seconds
timeoutSeconds: 2
# -- The readiness probe failure threshold
failureThreshold: 3
# -- The readiness probe success threshold
successThreshold: 1
autoscaling:
# -- Create a HorizontalPodAutoscaler for the API
enabled: false
# -- The minimum replicas for the API autoscaler
minReplicas: 1
# -- The maximum replicas for the API autoscaler
maxReplicas: 10
# -- The target CPU threshold for the API autoscaler
targetCPUUtilizationPercentage: 80
# -- The target memory threshold for the API autoscaler
# targetMemoryUtilizationPercentage: 80
# -- API resource limits and requests, our request recommendations are based on minimal requirements and the limit recommendations are based on usage in a high-traffic production environment.
# If you are running on environments like Minikube you may wish to remove these recommendations.
resources:
limits:
cpu: "1"
memory: 512Mi
requests:
cpu: 50m
memory: 64Mi
# -- API node selector
nodeSelector: {}
# -- API tolerations
tolerations: []
# -- API affinity
affinity: {}
# -- Add a sleep before the pod is stopped. This is useful if using the AWS ALB ingress controller to allow the controller to deregister the target before the pod is stopped.
# preStopSleepSeconds: 40
# -- The total time for the container to exit normally before being terminated. If specifying the preStopSleepSeconds, this value should be greater than that.
# terminationGracePeriodSeconds: 60
job:
# -- Run the job as a one-off on deploy
runInitJob: true
# -- Job backoff limit
backoffLimit: 6
# -- Job schedule
schedule: "0 4 * * SUN"
# -- Set this to debug, info, warn or error
logLevel: info
# -- History limit for successful jobs
successfulJobsHistoryLimit: 5
# -- History limit for failed jobs
failedJobsHistoryLimit: 5
# -- Deadline seconds for the job starting
startingDeadlineSeconds: 3600
# -- Job resource limits and requests.
# If you are running on environments like Minikube you may wish to remove these recommendations.
resources:
limits:
cpu: 200m
memory: 640Mi
requests:
cpu: 50m
memory: 128Mi
# -- Job node selector
nodeSelector: {}
# -- Job tolerations
tolerations: []
# -- Job affinity
affinity: {}