Operations | Monitoring | ITSM | DevOps | Cloud

This blog post is a how-to guide for Kubernetes troubleshooting. Our vision is that any engineer can keep Kubernetes-based applications up and running smoothly, regardless of their level of Kubernetes expertise and their knowledge of the services in the environment. Right out of the box, StackState aims to monitor, alert and then guide an engineer directly to the problem, helping them remediate the issue quickly.

Kubernetes has become the preferred tool for DevOps engineers to deploy and manage containerized applications on one or multiple servers. These compute nodes are also known as clusters, and their performance is crucial to the success of an application. If a Kubernetes cluster isn’t performing optimally, the application’s availability and performance will suffer, leading to unhappy users and even revenue loss.

Since the onset of the pandemic and the changes in working patterns that resulted from it, employee welfare has been boosted to the top of the agenda, with this new mindset seeming to be lasting. According to the UK’s Chartered Institute of Personnel and Development, 75% of employees believe senior leaders prioritize well-being as part of business operations.

Over the last couple of decades, a lot has changed in terms of how companies are running their infrastructure. The days of dedicated physical servers are long gone, and there are a variety of options for making the most out of your hosts, regardless of whether you’re running them on-prem or in the cloud. Virtualization paved the way for scalability, standardization and cost optimisation. Containerization brought new efficiencies.

Persistent storage is essential for any account-driven website. However, in Kubernetes, most resources are ephemeral and unsuitable for keeping data long-term. Regular storage is tied to the container and has a finite life span. Persistent storage has to be separately provisioned and managed. Making permanent storage work with temporary resources brings challenges that you need to solve if you want to get the most out of your Kubernetes deployments.

We’ve just released Calico v3.25! This milestone release includes a number of eBPF dataplane improvements designed to deliver an even faster upgrade experience, smaller memory footprint, and shorter eBPF networking object load time speed. But before we get into the details of these changes, let’s welcome and thank our new community problem-solvers who got their first contribution requests merged into our beloved project.