mirror of https://github.com/minio/minio.git
c0ac25bfff
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. |
||
|---|---|---|
| .. | ||
| api | ||
| cache | ||
| compress | ||
| etcd | ||
| identity | ||
| notify | ||
| policy/opa | ||
| storageclass | ||
| bool-flag.go | ||
| bool-flag_test.go | ||
| certs.go | ||
| certs_test.go | ||
| certsinfo.go | ||
| config.go | ||
| config_test.go | ||
| constants.go | ||
| errors-utils.go | ||
| errors.go | ||
| help.go | ||
| legacy.go | ||