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 (#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.

Author: solsson

50kafka.yml

@@ -51,7 +51,7 @@ spec:
         readinessProbe:
           tcpSocket:
             port: 9092
-          timeoutSeconds: 9
+          timeoutSeconds: 1
         volumeMounts:
         - name: config
           mountPath: /etc/kafka