Operations | Monitoring | ITSM | DevOps | Cloud

Kubernetes operators extend the Kubernetes API with custom logic, automating tasks like provisioning, configuration, and policy enforcement. Instead of managing these tasks manually or with ad hoc scripts, Operators codify your workflows into controllers that run natively inside the cluster. In this tutorial, you’ll build a simple operator using Go and Kubebuilder; a framework that scaffolds much of the boilerplate so you can focus on core logic.

AI has made it easier than ever to write code. Shipping it is a different story. Today we released the 2026 State of Software Delivery report, sponsored by Thoughtworks. In it, we analyzed more than 28 million CI/CD workflows across thousands of engineering teams. The picture that emerged is clear: teams are producing more code than ever, but fewer of them are able to turn that activity into software that actually reaches customers.

Following the end of maintenance of the Ingress NGINX project, we have been working behind the scenes to migrate our customers’ clusters from Kubernetes Ingress + NGINX Ingress Controller to Gateway API + Envoy Gateway.

AWS EC2, Azure Virtual Machines, and Google Compute Engine (GCE) appear similar on paper but produce different bills due to how each provider prices capacity, discounts, idle time, and commitment terms. The same VM configuration can cost 20-40% more or less depending on which cloud you choose and how your workload runs. On paper, all three offer similar virtual machines. In reality, they price capacity, discounts, and idle time very differently.

Deploying changes to Oracle databases can be complex from working across multiple schemas, handling dependencies, and accounting for environment differences. Flyway has been helping teams bring order and automation to Oracle development for over 15 years and in 2026 we’re accelerating that investment even further. Here’s a look at the latest enhancements available today and what’s coming next for Oracle users.

This month’s highlights include smarter dependency handling in Flyway Desktop, and a look at how we’re starting the year strong for Oracle users. Plus: last call to share your feedback in our Flyway user survey (the prize draw closes soon!).

When a database security incident happens, everyone turns to the security team. We look for a simple root cause analysis, and then we add a control, tighten a policy, and maybe even buy a silver bullet tool. We feel progress! But the incident didn’t start there. It started years earlier, when the organization made a series of perfectly reasonable decisions that quietly expanded the surface area and weakened the consistency of control.

In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams don’t explicitly decide what they want to happen as a result of a signal, they default to the loudest option available.