Explore >> Select a destination
|
You are here 
|
www.uptycs.com | ||
| | | | |
www.tremolosecurity.com
|
|
| | | | | Use OopenUnison to integration Active Directory and Cononical's Kubernetes Distribution! . | |
| | | | |
www.learnitguide.net
|
|
| | | | | Learn Kubernetes RBAC with real EKS examples. Control user access using Roles, Bindings & aws-auth. Includes step-by-step demo for 3 IAM users. | |
| | | | |
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)." ?? | |
| | | | |
haseebmajid.dev
|
|
| | | In this post, we will go over how we can deploy K3S on our PI cluster we have set up. Which is running NixOS, and we can also pass secrets using sops nix based on the previous parts of this series. Some of you maybe wondering what is K3S, it is a Kubernetes distribution which is tiny i.e. the binary is only 50 MB. It also has fewer dependencies. Make it perfect our PI cluster and home lab and IoT apps. I am still going to work out how to manage the Kubernetes cluster itself, perhaps I will use Pulumi you could also terraform if you wanted a reproducible PI cluster. | ||
