You are here |
carlosbecker.com | ||
| | | |
vadosware.io
|
|
| | | | How I went about setting up a HTTP application on Kubernetes, with Ingress | |
| | | |
mbuffett.com
|
|
| | | | There's no shortage of posts like "Let's use Kubernetes!" Now you have 8 problems, or Do I Really Need Kubernetes?, which tend to argue that unless you're orchestrating 1000 containers, you're good without Kubernetes. Also, I thought this tweet was hilarious: So... Hi, I'm the guy using Kubernetes for my blog and small side projects, here's why I love it (to the extent one can love a deploy tool). "You don't need all that complexity" Undoubtedly, Kubernetes is doing a lot under the hood. But as an end-user, I'm not exposed to that complexity. After spending a couple hours learning the key concepts through the official tutorial, it really is very easy to use day-to-day. | |
| | | |
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)." ?? | |
| | | |
hypernephelist.com
|
|
| | This article describes the steps to deploy the SUSE Cloud Application Platform (CAP) on Azure Kubernetes Service (AKS). SUSE Cloud Application Platform is a ... |