From 8e82d07fc692daed18af4166667b957a21d38d17 Mon Sep 17 00:00:00 2001
From: Chris Wedgwood <cw@f00f.org>
Date: Mon, 30 Oct 2017 20:10:57 +0000
Subject: [PATCH] rabbitmq: reasonable timing for readinessProbe

Give things time to start and probe only as needed.  This avoids
premature health warnings such as:

  Normal   Created                14s   kubelet, node-0    Created container
  Normal   Started                14s   kubelet, node-0    Started container
  Warning  Unhealthy              10s   kubelet, node-0    Readiness probe failed:

Change-Id: I224aed14a03a3690f1ba2a07a2d9fad54b7dd550
---
 rabbitmq/templates/deployment.yaml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/rabbitmq/templates/deployment.yaml b/rabbitmq/templates/deployment.yaml
index 095519734d..d971d6f264 100644
--- a/rabbitmq/templates/deployment.yaml
+++ b/rabbitmq/templates/deployment.yaml
@@ -49,6 +49,8 @@ spec:
               fieldRef:
                 fieldPath: status.podIP
           readinessProbe:
+            initialDelaySeconds: 30
+            periodSeconds: 30
             timeoutSeconds: {{ .Values.probes_timeout }}
             exec:
               command: