From b462dac8cfd33ccac4aec84fcf5f915cbfc135a3 Mon Sep 17 00:00:00 2001
From: Staffan Olsson <staffan@repos.se>
Date: Tue, 7 Nov 2017 12:57:01 +0100
Subject: Actually, for readiness not liveness, let's go offline fast ...

and trust alarms on Under-replicated Partitions to let us know
when something is really wrong.

Do clients actually care about Readiness?

The bootstrap service (https://github.com/Yolean/kubernetes-kafka/pull/52)
will definitely care, which is good.

The `broker` service, that the StatefulSet manifest depends on
(https://github.com/Yolean/kubernetes-kafka/blob/v2.1.0/50kafka.yml#L7)
for naming, is without `publishNotReadyAddresses`.

Clients will bootstrap, get the individual DNS names of brokers,
resolve those addresses and connect directly to pods.
---
 50kafka.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/50kafka.yml b/50kafka.yml
index cabbfad..50d0228 100644
--- a/50kafka.yml
+++ b/50kafka.yml
@@ -51,7 +51,7 @@ spec:
         readinessProbe:
           tcpSocket:
             port: 9092
-          timeoutSeconds: 9
+          timeoutSeconds: 1
         volumeMounts:
         - name: config
           mountPath: /etc/kafka
-- 
cgit v1.2.3