Explore >> Select a destination
|
You are here 
|
nbailey.ca | ||
| | | | |
hayl.in
|
|
| | | | | [AI summary] The article explains how to use GitHub Actions to build Docker images and trigger Kubernetes deployment rollouts by setting up service accounts and tickets. | |
| | | | |
haim.dev
|
|
| | | | | When you need to run something just once, but on each node | |
| | | | |
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)." ?? | |
| | | | |
actuated.com
|
|
| | | GitHub warns against using self-hosted Actions runners for public repositories - but why? And are there alternatives? | ||
