Operations | Monitoring | ITSM | DevOps | Cloud

Bare metal is BACK! For years virtualization has absolutely dominated the cloud market. The market for virtualization is still 10x larger than bare metal ($8B USD vs$100B USD). But now consumers are demanding MORE for their workloads. … and the signal from the data suggest that this trend isn't going away anytime soon. If we look a bit deeper, we might see another story enabling the avalanche of (re) adoption in bare metal.

In March 2025, Wiz researchers disclosed a set of critical vulnerabilities in the popular ingress-nginx controller for Kubernetes. Collectively referred to as IngressNightmare, these issues (CVE-2025-1097, CVE-2025-1098, CVE-2025-24513, CVE-2025-24514, and CVE-2025-1974) allow unauthenticated attackers to exploit the Ingress admission controller, potentially achieving remote code execution or escalating privileges in the cluster.

We’re excited to announce Kubesleep, a smart Kubernetes operator developed by SUSE that optimizes cluster efficiency and significantly reduces infrastructure costs. Kubesleep automatically scales workloads based on actual developer activity, intelligently detecting periods of inactivity and scaling down resources to save energy and expenses. Best of all, your clusters smoothly scale back up before developers even notice.

Without SQL aggregate functions, databases would be nothing more than glorified spreadsheets. These functions—SUM(), COUNT(), AVG(), MIN(), and MAX() —do the heavy lifting in analytics. They process massive datasets, transforming scattered records into clear, usable insights that drive decision-making. But while aggregation simplifies data, it can also slow things down.

Imagine spending weeks grinding through SQL tutorials, practicing syntax, and refining your queries in your spare time. But when the interviewer throws a complex JOIN + subquery at you, your brain suddenly hits a 404. It happens to the best of us. However, most candidates crash and burn—not because they lack knowledge, but because they prepare like students instead of engineers. They memorize syntax, pray for predictable questions, and freeze the moment they’re asked to think, not recite.

Server hardening is securing a server by reducing its surface of vulnerability. This means minimizing the number of potential entry points for attackers by disabling unnecessary services, applying patches, and enforcing strong security controls. If you use Kamal to deploy applications but you must harden your servers yourself. This is a guide on the steps to take to have a secure server. The Basics of Server Security: Patch often and restart often. Patching helps with fixing known vulnerabilities.

Recently we introduced support for Failure Strategies, which allows developers to implement more powerful logic and control flow into their workflows. Today, we are excited to announce a new step failure strategy, retry, which can auto-retry your failed steps without requiring any input from the user.

As your applications scale and generate more telemetry, it becomes increasingly difficult to sift through the data and analyze it against cost, business functions, and security measures. Logs, events, and other telemetry on their own may not include enough meaningful context or readable details, leading to slower troubleshooting, inefficient business processes, and higher costs.