Explore >> Select a destination
|
You are here 
|
linkerd.io | ||
| | | | |
www.buoyant.io
|
|
| | | | | Applying L4 network policies with a service mesh. In this tutorial, you'll learn how to run Linkerd and Cilium together and how to use Cilium to apply L3 and L4 network policies to a cluster running Linkerd. Linkerd is an ultralight, open source service mesh. Cilium is an open source CNI layer for... | |
| | | | |
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)." ?? | |
| | | | |
devopsian.net
|
|
| | | | | A deep-dive into progressive deployments, specifically Canary, on Kubernetes with Flagger using ingress-controller or a service mesh. How it works? I ran into some pitfalls and wrote about it, so you don't need to solve it too. | |
| | | | |
jenkins-x.io
|
|
| | | Analyzing results | ||
