Operations | Monitoring | ITSM | DevOps | Cloud

Kubernetes 1.33 is right around the corner, and there are quite a lot of changes to unpack! Removing enhancements with the status of “Deferred” or “Removed from Milestone” we have 64 Enhancements in all listed within the official tracker. So, what’s new in 1.33? Kubernetes 1.33 brings a whole bunch of useful enhancements, including 35 changes tracked as ‘Graduating’ in this Kubernetes release.

Over the last three months, we’ve focused on solving three core challenges our users face: delivering faster, improving resiliency, and gaining tighter control over cloud infrastructure. Today, we’re excited to share the new features we rolled out in Q1 2025 - all built to help teams ship faster, with more confidence, and lower operational overhead.

Your containers are running, nd your clusters seem fine, but then you get that dreaded alert – memory pressure. Whether you're scaling up your infrastructure or just trying to keep things running smoothly, understanding pod memory usage isn't just nice to have – it's essential knowledge for any DevOps engineer worth their salt. Let's cut through the noise and get straight to what matters: practical ways to track, analyze, and fix memory issues in your Kubernetes pods.

This guide covers container port configurations in Kubernetes, explaining key concepts and practical setups. If you're setting up ports for the first time or troubleshooting connectivity issues, you'll find clear explanations and useful examples to help you navigate container networking effectively.

Docker containers continuously generate logs during operation, and without proper management, these logs can consume significant disk space, impact system performance, and create operational issues. Logrotate offers an effective solution for managing these logs in containerized environments. This guide covers the implementation of logrotate in Docker containers – from initial setup through advanced configurations that ensure stable, maintainable container deployments.

In today’s fast-paced development landscape, containerization has become a cornerstone for deploying scalable and efficient applications. Docker, as one of the most popular container platforms, offers a robust environment for building and running containers. However, with great power comes the need for greater scrutiny, i.e., Docker monitoring or observability. Understanding Docker metrics is key to maintaining optimal performance and ensuring your containerized applications run smoothly.

Choosing the right Container Network Interface (CNI) for Kubernetes is critical to achieving optimal performance, security, and scalability. With the launch of Canonical Kubernetes LTS (long-term support) last month, Canonical decided to integrate Cilium as the default CNI in order to reflect our commitment to delivering a modern, security-maintained, high-performance Kubernetes experience.