Operations | Monitoring | ITSM | DevOps | Cloud

Previously, we showed you how to securely pull Docker images from Cloudsmith to Kubernetes using OIDC with a CronJob-based approach. We concluded the post discussing credential provider plugins from Kubernetes 1.20 and an enhancement in Kubernetes 1.33 that offers a new approach for external registries like Cloudsmith. We have now built a credential provider that takes advantage of this new capability. This article explores what this means for the future of pulling images from Cloudsmith on Kubernetes.

Managing permissions in sprawling Kubernetes landscapes can often feel like untangling an ever-growing knot. As clusters and user bases expand, so does the intricate web of RoleBindings, impacting everything from UI responsiveness to the very stability of etcd. This complexity, if unaddressed, can become a significant hurdle to achieving scalability and maintaining optimal performance in Rancher. SUSE is committed to improving its container management platform.

In the simplest of terms, container orchestration is the automated process of deploying, managing, scaling and networking containers. Containers are lightweight, portable self contained units that include an application or the processes needed to run applications. Docker is a great example of a project that helps to containerize or package applications, and was a large reason why containers gained such popularity around 2013. Before Docker there were Linux Containers (LXC).

Trends in tech come and go, but certain underlying primitives stick around forever. In software, two such primitives are virtual machines and containers. Virtualization paved the way for the cloud to become massive. Data centers would likely never have been commercially viable without it. While still relatively new, containerization has already made a serious mark on the software engineering world.

What if you were to tell Kubernetes Monitoring what you wanted, and the system configured collectors based on your choices? We wondered that as well—wondered enough to create Alloy Operator and its Helm chart for version 3.0 of the Kubernetes Monitoring Helm chart. We’re excited to share that the new Kubernetes Monitoring Helm chart is now available, and it introduces a dynamic way of setting up your telemetry data collection with Alloy Operator.

We are in mid-2025, and teams across industries are rolling out large language models, or LLMs, to power everything from conversational agents to document understanding. However, getting them to run smoothly in production… That’s still a challenge. A working model isn’t just about putting it in a container and tossing it into a Kubernetes cluster.

Kubernetes makes it easy to scale applications. But when it comes to CPU resource management, a poorly tuned cluster can quickly become unstable or inefficient. For network engineers, setting CPU requests and limits correctly—and understanding the deeper implications—is essential for keeping workloads efficient, costs predictable, and noisy neighbors in check.

We are thrilled to announce the next major milestone in our platform vision: Qovery observability! Qovery Observability is our new product, ready to give you the fastest way to gain a crystal-clear, unified understanding of your application and infrastructure. Fully managed, zero lock-in, you keep the data. Devs love it, no DevOps needed. Coming soon!

Kubernetes excels at managing complex, containerized systems, and one of its most impactful patterns is the sidecar. Sidecar containers extend applications by running supplementary processes in tandem. This modular architecture enables enhanced observability, networking, or security layers — all without changing the core application code. Continuous Integration and Continuous Deployment (CI/CD) practices are key to reliably shipping these configurations.