From c4ff58480a97f80665c2999060790e2b0966e988 Mon Sep 17 00:00:00 2001
From: Waldemar Faist <cubic@coldice.net>
Date: Fri, 19 Mar 2021 10:34:19 +0100
Subject: [PATCH] fix: missing probe timeout value

---
 charts/stable/deconz/values.yaml | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/charts/stable/deconz/values.yaml b/charts/stable/deconz/values.yaml
index 274c5d2a..48b437eb 100644
--- a/charts/stable/deconz/values.yaml
+++ b/charts/stable/deconz/values.yaml
@@ -60,7 +60,8 @@ serviceAccount:
 # -- Key-value pairs to add as pod annotations
 podAnnotations: {}
 
-podSecurityContext: {}
+podSecurityContext:
+  {}
   # fsGroup: 2000
 
 securityContext:
@@ -140,7 +141,8 @@ ingress:
   # -- Enables Ingress
   enabled: false
   # -- Ingress annotations
-  annotations: {}
+  annotations:
+    {}
     # kubernetes.io/ingress.class: nginx
     # kubernetes.io/tls-acme: "true"
   # -- Custom labels
@@ -157,7 +159,8 @@ ingress:
   #      - deconz.local
 
 # -- CPU/Memory resource requests/limits
-resources: {}
+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
@@ -187,6 +190,7 @@ probes:
     # -- Specify readiness `failureThreshold` parameter for the Pod
     failureThreshold: 5
     # -- Specify readiness `timeoutSeconds` parameter for the Pod
+    timeoutSeconds: 10
   startup:
     # -- Enables startup probe for the Pod
     enabled: false