Explore >> Select a destination
|
You are here 
|
blog.elksoft.pl | ||
| | | | |
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)." ?? | |
| | | | |
blog.zespre.com
|
|
| | | | | As you may have already known, I have a 4-node Kubernetes cluster, which was installed using kubeadm. When I was trying to deploy metrics-server on my cluster using the official Helm chart, I got the following situation: | |
| | | | |
gist.github.com
|
|
| | | | | Script which access the Jamf Pro API and uses provided API client authentication to obtain and verify bearer tokens - jamf_pro_api_client_token_management.sh | |
| | | | |
www.mathieupassenaud.fr
|
|
| | | [AI summary] The article argues for securing user accounts by minimizing the number of passwords stored and utilizing robust authentication protocols like OAuth, OpenID, and WebAuthn provided by major services, suggesting password managers and hardware keys as effective alternatives. | ||
