Explore >> Select a destination
|
You are here 
|
www.nocentino.com | ||
| | | | |
bioconductor.github.io
|
|
| | | | | Build and test for Linux ARM64 with Docker on x86_64 host | |
| | | | |
alexos.dev
|
|
| | | | | My blog about interesting technology - and in particular Cloud Platforms & Services, and my experiences with them | |
| | | | |
www.salvis.com
|
|
| | | | | Database centric development | |
| | | | |
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)." ?? | ||
