/explore
|
You are here 
|
haim.dev | ||
| | | | |
jb3.dev
|
|
| | | | | AlertManager is a rock solid approach for alerting in Prometheus, but how do you make it highly available on Kubernetes? This article covers my approach to making AlertManager highly available on Kubernetes, and how you can do the same. | |
| | | | |
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)." | |
| | | | |
nikdoof.com
|
|
| | | | | vCluster is a great tool for anyone managing larger Kubernetes clusters which may contain multiple users, environments, a need for larger isolation between workloads. For me vCluster works brilliantly as a method of testing new applications in a disposable cluster where I can run some of the larger, more integrated operators and tooling without much fear of interfering with my existing Kubernetes setup. In my cluster I make use of Flux to manage my manifest and resources in a GitOps method, and using vCluster with Flux and a dash of OIDC makes for an excellent user experience. | |
| | | | |
bryanbende.com
|
|
| | | [AI summary] This blog post explains how to set up and test ingress in a K3s cluster using Traefik and the Klipper load balancer, with an example application demonstrating the setup. | ||
