1. “Two-node HA Kubernetes for edge computing cost savings” by Tyler Gillson, Spectro Cloud.
"[..] three node Kubernetes clusters provide stronger guarantees with arguably less architectural complexity, yet they impose massive capital expenditure at scale, not only in the cost of the boxes themselves, but cabling, shipping, software, power consumption and other factors. If you’re looking to optimize costs or an edge compute use case, a two node solution can instantly cut costs and materialize serious savings.”
2. “Load balancing and scaling long-lived connections in Kubernetes” by Daniele Polencic, Learnk8s.
“Kubernetes doesn't load balance long-lived connections, and some Pods might receive more requests than others. Consider client-side load balancing or a proxy if you're using HTTP/2, gRPC, RSockets, AMQP, or any other long-lived database connection.”
3. “Learned it the hard way: Don’t use Cilium’s default Pod CIDR” by Isala Piyarisi, WSO2.
“Despite extensive testing, complex systems like Cilium, with nearly 2000 configurable values, can still allow misconfigurations to slip though which could lead to unexpected failures. This incident taught us the importance of methodically troubleshooting network issues and understanding low-level networking infrastructure and skills, often taken away by cloud abstractions.”
4. “Optimizing Application Resilience: A Deep Dive into Kubernetes Pod Disruption Budgets and Rollout Strategies” by Nicolas Labrot, ARHS Spikeseed.
“By effectively implementing both PDBs and rollout strategies, you can enhance the resilience and reliability of your Kubernetes-managed applications, ensuring they remain stable and available even during disruption and updates.”
5. “From Fragile to Faultless: Kubernetes Self-Healing In Practice” by City Storage Systems.
“In this blog we share our experience illustrating how minor glitches, if left unattended, could quickly escalate and impact business continuity. Rather than engaging in constant firefighting we designed a self-healing framework, often implementing automations with a turnaround time of as little as 1 day. [..] While our journey began with a focus on AKS, this framework is a general-purpose pattern to improve resilience of any Kubernetes platform.”
#articles