fix(boot.go,src/healthsrv): add readiness and liveness probes#57
Conversation
| version: bb44bb2e4817fe71ba7082d351fd582e7d40e3ea | ||
| - name: github.com/fsouza/go-dockerclient | ||
| version: 76fd6c68cf24c48ee6a2b25def997182a29f940e | ||
| version: "" |
There was a problem hiding this comment.
I'm not sure why glide did this. Investigating...
There was a problem hiding this comment.
@bacongobbler after running glide up again (more precisely, make glideup), this version number didn't come back. In arschles@08099c9, however, another version number did come back for a launchpad.net dependency...
@technosophos suggested that I file an issue on glide for this, so I'm working on getting a solid set of repro steps down before I do.
57fe51e to
74015a7
Compare
|
I'm torn on whether it might be better to create the minio client used by the health check in / closer to the healthcheck code instead of doing so in |
and a single health check endpoint ‘/healthz’
so that the health check server can use it to check the health of the minio server
and add a test for it
also specify the health check server port
…tch the default …while still keeping it explicitly defined
…ace for listing buckets The Go minio client adheres to it, and it will be used for more easily testing the healthz endpoint handler. The alternative was to use this interface: https://godoc.org/github.com/minio/minio-go#CloudStorageClient …
611c4c5 to
4e774e9
Compare
|
@krancour good point, and thanks for that. I think the other option for minio client creation location is in the |
gets a version back for launchpad
|
This code looks good to me once the |
also re-run ‘glide up’, which adds versions back in for github repositories. finally, set the minio version to latest (as of this writing)
|
@mboersma @bacongobbler after running a |
| version: 68415e7123da32b07eab49c96d2c4d6158360e9b | ||
| repo: https://github.com/golang/protobuf | ||
| version: "" | ||
| repo: https://code.google.com/p/goprotobuf |
There was a problem hiding this comment.
code.google.com no longer exists. Any idea how this would occur?
There was a problem hiding this comment.
no idea. glide seems to toggle that just about every time I run glide up
fix(boot.go,src/healthsrv): add readiness and liveness probes
Fixes #54
After this is merged and a new container is built, deis/charts#86 needs to be done