G2

Gene G.

Director of Marketing

Medical Devices

Small-Business (50 or fewer emp.)

4/7/2026

"Reduced Manual Upgrade Work and gave our small team leverage."

5/5

What do you like best about Kubegrade?

The biggest win is time. What used to be a two week effort per major upgrade is now two to three days including testing. We also caught a breaking change in a CRD that would have taken down a critical workload. That single catch justified the investment. The centralized cluster view is great for a small team. Instead of SSHing into clusters or checking dashboards one by one, we get a single pane showing lifecycle risks across everything we manage. Review collected by and hosted on G2.com.

What do you dislike about Kubegrade?

A few of the newer features are still maturing, and documentation could be more detailed in places. But for a small team that needs to punch above its weight on kubernetes operations, kubegrade is exactly what we needed. I would recommend it to any lean platform everything we manage. Review collected by and hosted on G2.com.

What problems is Kubegrade solving and how is that benefiting you?

We are a two person team responsible for eight kubernetes clusters. Every K8s version bump was a multi week project involving manual deprecation checks, testing, coordination with app teams, and a lot of anxiety about what we might have missed.

We chose Kubegrade because it automates the parts of upgrade preparation that consumed most of our time: scanning for deprecated APIs, checking resource compatibility, and generating the remediation changes. The fact that it works through Git pull requests was important because we could review everything before it touched our clusters.

We use it for every upgrade cycle now, plus ongoing monitoring for drift and new deprecation warnings as upstream kubernetes releases happen. It has become part of our standard operating procedure. Review collected by and hosted on G2.com.