 
      
    | You are here | ekhabarov.com | ||
| | | | | jreypo.io | |
| | | | | The easiest way to have a Kubernetes cluster up and running in Azure in a short amount of time is by using AKS service, also if you want a more granular control of your cluster or a more customized cluster you can alway use AKS-Egine. | |
| | | | | 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)." ?? | |
| | | | | martinheinz.dev | |
| | | | | As your project grows, it might get to the point that it becomes too hard to handle with just single VM or some simple SaaS solution. You can solve tha... | |
| | | | | vadosware.io | |
| | | Modifying a recently created Container Linux ignition configuration to use rkt and kube-router (instead of containerd and canal). | ||