Last active
November 17, 2023 15:32
-
-
Save nitisht/0c11d8c670f565b58d930b526ba0f2ed to your computer and use it in GitHub Desktop.
Revisions
-
nitisht revised this gist
Feb 28, 2018 . 1 changed file with 1 addition and 1 deletion.There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -13,7 +13,7 @@ Kubernetes *does not* forward traffic to pods if readiness probe responds with a ### Minio implementation Minio server exposes two un-authenticated, healthcheck related endpoints - liveness probe and readiness probe at `/minio/health/live` and `/minio/health/ready` respectively. - Liveness probe handler does a list buckets internally, if that is successful, server returns a status 200 OK. If it fails, it returns 503. - Readiness probe handler does a go routine count internally. If the number of go routines is higher than a threshold, server returns 503 else it returns 200. Currently the arbitrary threshold for total goroutines is set to 500. -
Feb 28, 2018 . 1 changed file with 1 addition and 1 deletion.There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -11,7 +11,7 @@ Used to identify situations where server is not ready to accept requests yet. Su Kubernetes *does not* forward traffic to pods if readiness probe responds with a failure code. It just waits for the readiness probe to return success. ### Minio implementation Minio server exposes two un-authenticated, healthcheck related endpoints - liveness probe and readiness probe at `/minio/health/live` and `/minio/health/ready` respectively. - Liveness probe handler does a list object internally, if that is successful, server returns a status 200 OK. If it fails, it returns 503. - Readiness probe handler does a go routine count internally. If the number of go routines is higher than a threshold, server returns 503 else it returns 200. Currently the arbitrary threshold for total goroutines is set to 500. -
Feb 28, 2018 . 1 changed file with 1 addition and 1 deletion.There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -11,7 +11,7 @@ Used to identify situations where server is not ready to accept requests yet. Su Kubernetes *does not* forward traffic to pods if readiness probe responds with a failure code. It just waits for the readiness probe to return success. ### Minio implementation Minio server exposes two healthcheck related endpoints, liveness probe and readiness probe at `/minio/health/live` and `/minio/health/ready` respectively. Both are un-authenticated. - Liveness probe handler does a list object internally, if that is successful, server returns a status 200 OK. If it fails, it returns 503. - Readiness probe handler does a go routine count internally. If the number of go routines is higher than a threshold, server returns 503 else it returns 200. Currently the arbitrary threshold for total goroutines is set to 500. -
Feb 28, 2018 . 1 changed file with 19 additions and 5 deletions.There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -1,15 +1,29 @@ ## Minio Healthcheck ### Liveness probe definition Used to identify situations where server is running but may not behave optimally, i.e. sluggish response or corrupt backend. Such situations can be generally *only* be fixed after a restart. Kubernetes *kills* the container and restarts it in case of liveness probe responding with a failure code. ### Readiness probe definition Used to identify situations where server is not ready to accept requests yet. Such situations are generally recovered after waiting for some time. Kubernetes *does not* forward traffic to pods if readiness probe responds with a failure code. It just waits for the readiness probe to return success. ### Minio implementation Minio server exposes two healthcheck related endpoints, liveness probe and readiness probe at `/minio/health/live` and `/minio/health/ready` respectively. - Liveness probe handler does a list object internally, if that is successful, server returns a status 200 OK. If it fails, it returns 503. - Readiness probe handler does a go routine count internally. If the number of go routines is higher than a threshold, server returns 503 else it returns 200. Currently the arbitrary threshold for total goroutines is set to 500. Sample configuration in a Kubernetes `yaml` file. ```yaml livenessProbe: httpGet: path: /minio/health/live port: 9000 initialDelaySeconds: 10 periodSeconds: 20 ``` -
Feb 28, 2018 . 1 changed file with 12 additions and 1 deletion.There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -1,4 +1,15 @@ ## Minio healthcheck endpoints Expose two healthcheck related endpoints, liveness probe and readiness probe at `/minio/health/live` and `/minio/health/ready` respectively. ### Liveness probe definition Used to identify situations where server is running but may not behave optimally, i.e. sluggish response. Such situations can be generally fixed after a restart. Kubernetes *kills* the container and restarts it in case of liveness probe responding with a failure code. ### Readiness probe definition Used to identify situations where server is not ready to accept requests yet. Such situations are generally recovered after waiting for some time. A pod with containers reporting that they are not ready do not receive traffic through Kubernetes Services. ### Minio implementation -
Feb 28, 2018 .There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -0,0 +1,4 @@ ## Minio healthcheck endpoints Expose two healthcheck related endpoints - liveness probe and readiness probe at `/minio/health/live` and `/minio/health/ready` respectively.