Harshavardhana c0ac25bfff fix: readiness needs to be like liveness (#9941) ... Readiness as no reasoning to be cluster scope because that is not how the k8s networking works for pods, all the pods to a deployment are not sharing the network in a singleton. Instead they are run as local scopes to themselves, with readiness failures the pod is potentially taken out of the network to be resolvable - this affects the distributed setup in myriad of different ways. Instead readiness should behave like liveness with local scope alone, and should be a dummy implementation. This PR all the startup times and overal k8s startup time dramatically improves. Added another handler called as `/minio/health/cluster` to understand the cluster scope health.		2020-06-30 11:28:27 -07:00
..
api.go	simplify context timeout for readiness (#9772)	2020-06-04 14:58:34 -07:00
help.go	fix: readiness needs to be like liveness (#9941)	2020-06-30 11:28:27 -07:00