As a developer, it can become challenging to manage Kubernetes and develop applications simultaneously. That’s why we put together this guide to show you how the Kubernetes Dashboard can help developers overcome this problem and get an overview of the cluster and its workloads. From this, developers can focus more on application development while stressing less on cluster management.

Engineering teams’ autonomy and agility are vital in achieving efficient software development. However, manual infrastructure provisioning is a major source of inefficiency and bottleneck. As the developers wait for Ops teams to provision complex infrastructure, they cannot bring the creativity, speed, and agility expected of them. This is the reason successful companies are quickly adopting self-service infrastructure.

Recently I started hearing more and more about developer experience, which to me was a bit new-ish, so seriously what is developer experience? Another buzz word? A real thing? It’s been a while since I actually developed code … yes yes … you can laugh … a sales person that used to be a developer 😃, and A LOT changed since then. The number of tools a developer should work with on a daily basis is just crazy.

Kubernetes 1.26 is about to be released, and it comes packed with novelties! Where do we begin? This release brings 37 enhancements, on par with the 40 in Kubernetes 1.25 and the 46 in Kubernetes 1.24. Of those 37 enhancements, 11 are graduating to Stable, 10 are existing features that keep improving, 16 are completely new, and one is a deprecated feature. Watch out for all the deprecations and removals in this version!

Kubernetes can generate so many types of new metrics (millions every day) that one of the most complex aspects of monitoring your cluster’s health is filtering through these metrics to decide which ones are important to pay attention to. In fact, in a survey that Circonus conducted of Kubernetes operators, uncertainties around which metrics to collect was one of the top challenges to monitoring that operators face.

A recent Wall Street Journal article cited a KPMG survey that showed that roughly 67% of 1,000 senior technology leaders at U.S. firms across industries said they have yet to see a significant return on cloud investments. The most common issues preventing a better return on cloud spending were insufficient skills of tech teams, additional security and compliance requirements, and a misalignment with expected outcomes, said Barry Brunsman, a principal in KPMG’s CIO Advisory group.

Kubernetes is today the most well-known container scheduler used by thousands of companies. Being able to quickly and automatically scale your application is something standard nowadays. However, knowing how to do it well is another topic. In this article, we'll cover how pod autoscaling works, how it can be used, when it's exciting and not, and finally, we'll cover it with a Qovery usage we have internally.