If you’re a platform engineer or SRE, you know that managing infrastructure and efficiently managing it are two very different things. You’ve been able to run virtual machines (VMs) alongside containers in Red Hat Advanced Cluster Management (RHACM) for a while now. But as your fleet grows, finding that one specific VM acting up in a haystack of clusters can feel like a scavenger hunt you didn't sign up for.
Red Hat Advanced Cluster Management for Kubernetes 2.15 redefines your daily workflow instead of just adding features. We’ve taken the capabilities you rely on and made them easier to use so you can stop hunting and start solving.
Here are three ways RHACM 2.15 helps your fleet operations.
1. Stop digging for your VMs
In version 2.15, we overhauled the experience with a new fleet virtualization perspective.
- See the forest and the trees: A new tree view lets you visualize your entire fleet hierarchy instantly.
- Cut the noise: We added filtering by namespace, project, or folder so you can drill down to the exact workload you need without the clutter.
- Fix it faster: Once you find that VM, you can access it using VNC or SSH or migrate it live to another cluster to balance your fleet, all without leaving the console.
- Ops with clarity: You can see key facts like node, IP address, and storage class in a table and take multi-select actions like start, stop, restart, or pause.
The benefit: You spend less time clicking through menus (context switching) and more time managing your fleet.
2. Stop guessing on resources (and wasting money)
We all have that fear of under-provisioning a workload and causing an outage. So, what do we do? We over-provision "just in case." But across a massive fleet, those extra CPU cores and gigabytes of RAM add up to a seriously wasted budget.
RHACM 2.15 improves on right-sizing recommendations (Tech Preview) by analyzing your real-time resource consumption against what you originally requested. This information shows you where you are over-provisioned or under-utilized.
The benefit: You get data-driven recommendations to optimize your infrastructure usage without risking performance.
3. Scale GitOps to the edge
Managing ten clusters is hard. Managing hundreds across edge locations with spotty internet is a nightmare. Traditional push-based GitOps models often fail on air-gapped or restricted networks. Other pull models require a heavier footprint, which does not work well at small edge sites.
We’re introducing the Argo CD agent (Tech Preview) to change how this works. Instead of the control plane trying to force updates out to remote clusters, or large resource requirements being necessary for pulls, a lightweight agent on the edge reaches back to the hub and ensures round trip commit/reconciliation. This "pull model" is perfect for retail or manufacturing sites where the network is unreliable.
If you run large fleets, our global hub now supports managed cluster migration (general availability), letting you rebalance managed clusters and their workloads across hubs.
The benefit: You can scale your GitOps workflows to thousands of clusters, even in the most challenging edge environments, without losing control.
Ready to upgrade your workflow?
Infrastructure is complex, but managing it doesn't have to be a struggle. Red Hat Advanced Cluster Management for Kubernetes 2.15 is available now to help you see more, click less, and get your nights and weekends back.
Explore the Red Hat Advanced Cluster Management product page and the technical documentation to learn more.
