This in-depth article by Henrik Gerdes benchmarks various container runtime interfaces (CRIs) for Kubernetes. It provides a detailed comparison of runc, crun, gvisor, and youki, focusing on performance and memory consumption.
https://henrikgerdes.me/blog/2024-07-kubernetes-cri-bench/
https://henrikgerdes.me/blog/2024-07-kubernetes-cri-bench/
henrikgerdes.me
Benchmarking what actually drive our containers
Kubernetes success and versatility often overshadows the lower-level details of what actually drives our containers. I took a deeper took on how the default con…
👍2
This blogpost explores the statistical complexities of using Mean Time to Resolve (MTTR) as a key incident metric. The author argues that due to the power-law distribution of incident durations, MTTR trends can be misleading.
https://surfingcomplexity.blog/2024/12/01/mttr-when-sample-means-and-power-laws-combine-trouble-follows/
https://surfingcomplexity.blog/2024/12/01/mttr-when-sample-means-and-power-laws-combine-trouble-follows/
Surfing Complexity
MTTR: When sample means and power laws combine, trouble follows
Think back on all of the availability-impacting incidents that have occurred in your organization over some decent-sized period, maybe a year or more. Is the majority of the overall availability im…
👍2
kubectl-validate is a SIG-CLI subproject to support the local validation of resources for native Kubernetes types and CRDs.
https://github.com/kubernetes-sigs/kubectl-validate
https://github.com/kubernetes-sigs/kubectl-validate
GitHub
GitHub - kubernetes-sigs/kubectl-validate
Contribute to kubernetes-sigs/kubectl-validate development by creating an account on GitHub.
❤🔥1
This write-up from incident.io introduces the "Incident Maturity Model," a framework for evaluating and improving an organization's incident management processes. The model outlines three stages: Centralized, Distributed, and Democratized, offering a roadmap for growth.
https://incident.io/blog/the-incident-maturity-model
https://incident.io/blog/the-incident-maturity-model
incident.io
The Incident Maturity Model | Blog
Incidents are inevitable—how you handle them matters. The Incident Maturity Model shows how to level up from basic response to company-wide resilience, with actionable steps backed by real data. Where does your team stand?
👍1
Lawrence Jones provides an analysis of the challenges and incentives surrounding company status pages. The text delves into why transparency can be difficult for businesses, especially when SLAs and financial penalties are involved.
https://blog.lawrencejones.dev/status-pages/
https://blog.lawrencejones.dev/status-pages/
blog.lawrencejones.dev
Uptime, status pages, and transparency calculus
From the evergreen AWS status page to hardcoded 100% uptime, no one fully trusts a status page anymore. But why is this? Companies often start with good intentions, aiming for full transparency. So why do so many change along the way: what pressures people…
🔥1
This tutorial from Steven Sklar on DEV Community explains how to implement Kubernetes-powered leader election in Go applications. It walks through the use of Kubernetes Leases and the
https://dev.to/sklarsa/how-to-add-kubernetes-powered-leader-election-to-your-go-apps-57jh
client-go/tools/leaderelection package with a practical code example.https://dev.to/sklarsa/how-to-add-kubernetes-powered-leader-election-to-your-go-apps-57jh
DEV Community
How to add Kubernetes-powered leader election to your Go apps
Learn about leader election and how you can leverage part of the Kubernetes standard library to add this feature to your next application
👍1
This comprehensive guide details the process of setting up a high-availability k3s Kubernetes cluster. It uses keepalived for a virtual IP, a Galera cluster for the database, and Longhorn for distributed block storage to ensure no single point of failure.
https://raymii.org/s/tutorials/High_Available_k3s_kubernetes_cluster_with_keepalived_galera_and_longhorn.html
https://raymii.org/s/tutorials/High_Available_k3s_kubernetes_cluster_with_keepalived_galera_and_longhorn.html
👍2
⚠️ Ingress Nginx will be retired!
To prioritize the safety and security of the ecosystem, Kubernetes SIG Network and the Security Response Committee are announcing the upcoming retirement of Ingress NGINX 🪦
https://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement/
To prioritize the safety and security of the ecosystem, Kubernetes SIG Network and the Security Response Committee are announcing the upcoming retirement of Ingress NGINX 🪦
https://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement/
Kubernetes
Ingress NGINX Retirement: What You Need to Know
To prioritize the safety and security of the ecosystem, Kubernetes SIG Network and the Security Response Committee are announcing the upcoming retirement of Ingress NGINX. Best-effort maintenance will continue until March 2026. Afterward, there will be no…
1😢4❤2🎉2💩1