You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

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.		4 years ago
..
bigdata	…
bucket	…
chroot	…
compression	…
config	fix: readiness needs to be like liveness (#9941)	4 years ago
debugging	…
deployment/kernel-tuning	…
disk-caching	…
distributed	…
docker	…
erasure	…
federation/lookup	…
gateway	…
integrations/veeam	…
kms	…
lifecycle	…
logging	…
metrics	fix: readiness needs to be like liveness (#9941)	4 years ago
multi-tenancy	…
multi-user	…
orchestration	…
retention	…
screenshots	…
security	…
select	…
shared-backend	…
sts	…
throttle	…
tls	…
zh_CN	…
minio-limits.md	…