Explore >> Select a destination
|
You are here 
|
memo.mx | ||
| | | | |
pliutau.com
|
|
| | | | | Software Engineering Lead with a passion for APIs, Web, Cloud, Microservices, DevOps, Kubernetes etc. Engineering Lead at solsten.io | |
| | | | |
hjr265.me
|
|
| | | | | Docker has been providing a health check mechanism for quite some time. It is useful in identifying issues with programs that can fail in ways other than just outright crashing. And it is easy to set up. Docker health checks work periodically running a program within the container and observing its exit status. If it exits with a 0, the container is considered healthy. If it exits with a 1, the container is considered to be unhealthy. | |
| | | | |
www.neerajsidhaye.com
|
|
| | | | | Creating optimized docker image for GO application using multi stage build - using alpine image and then produce a small image with only binary in a scratch image. Let's read further... | |
| | | | |
blog.nuculabs.de
|
|
| | | Hi ?????, In this article I will talk about how to authenticate your applications to the Kubernetes API via the service accounts feature. Citing the Kubernetes docs, a service account for a pod: "provides an identity for processes that run in a Pod. When you (a human) access the cluster (for example, using kubectl), you are authenticated by the apiserver as a particular User Account (currently this is usually admin, unless your cluster administrator has customized your cluster). Processes in containers inside pods can also contact the apiserver. When they do, they are authenticated as a particular Service Account (for example, default)." ?? | ||
