mirror of
https://github.com/helm/charts.git
synced 2026-08-23 22:37:45 +00:00
Adding liveness probe timeout variable ➕ (#15146)
Signed-off-by: johndaviesco <john.davies-colley@xero.com>
This commit is contained in:
committed by
Kubernetes Prow Robot
parent
220d820cc6
commit
75fe62a37f
@@ -1,7 +1,7 @@
|
||||
apiVersion: v1
|
||||
name: aws-alb-ingress-controller
|
||||
description: A Helm chart for AWS ALB Ingress Controller
|
||||
version: 0.1.9
|
||||
version: 0.1.10
|
||||
appVersion: "v1.1.2"
|
||||
engine: gotpl
|
||||
home: https://github.com/kubernetes-sigs/aws-alb-ingress-controller
|
||||
|
||||
@@ -58,6 +58,7 @@ The following tables lists the configurable parameters of the alb-ingress-contro
|
||||
| `image.pullPolicy` | controller container image pull policy | `IfNotPresent` |
|
||||
| `enableReadinessProbe` | enable readinessProbe on controller pod | `false` |
|
||||
| `enableLivenessProbe` | enable livenessProbe on controller pod | `false` |
|
||||
| `livenessProbeTimeout` | How long to wait before timeout (in seconds) when checking controller liveness | 1 |
|
||||
| `extraEnv` | map of environment variables to be injected into the controller pod | `{}` |
|
||||
| `volumesMounts` | volumeMounts into the controller pod | `[]` |
|
||||
| `volumes` | volumes the controller pod | `[]` |
|
||||
|
||||
@@ -77,6 +77,7 @@ spec:
|
||||
scheme: HTTP
|
||||
initialDelaySeconds: {{ add .Values.livenessProbeInitialDelay .Values.readinessProbeInitialDelay }}
|
||||
periodSeconds: 60
|
||||
timeoutSeconds: {{ .Values.livenessProbeTimeout }}
|
||||
{{- end }}
|
||||
resources:
|
||||
{{ toYaml .Values.resources | indent 12 }}
|
||||
|
||||
@@ -63,6 +63,9 @@ enableLivenessProbe: false
|
||||
# How long to wait (in seconds) before checking the liveness probe
|
||||
livenessProbeInitialDelay: 30
|
||||
|
||||
# How long to wait before timeout (in seconds) when checking controller liveness
|
||||
livenessProbeTimeout: 1
|
||||
|
||||
rbac:
|
||||
## If true, create & use RBAC resources
|
||||
##
|
||||
|
||||
Reference in New Issue
Block a user