GitHub vs Komodor

The platform keeps widening what it can see. Kubernetes Add-ons make operator-managed workloads first-class: Komodor detects CRDs from KEDA, Strimzi, Flink, External Secrets, RabbitMQ, Cilium, and Kyverno in beta, with Gatekeeper, Vault, Calico, and Crossplane named next, and gives them health, configuration, and relationship views. Gateway API resources — GatewayClasses, Gateways, HTTPRoutes, GRPCRoutes — appear under the Network tab with the same inspection experience as Deployments. Services gained an Overview tab that leads with deployment status, pod health, and reliability signals instead of an events list that is often empty. Klaudia, the assistant, is invokable from any screen against a chosen cluster and keeps a searchable history of past investigations.

The through-line is coverage, then explanation. Komodor's value depends on the cluster map being complete, and the recent work fills the two biggest holes in that map — operator-managed custom resources and the Gateway API — before layering Klaudia over them for root-cause analysis. The assistant work follows the same order: first make it reachable and persistent, then let it read customer runbooks and reason over the resources the platform now understands. Argo CD and Argo Rollouts support earlier in the window is the same move applied to deployment tooling.

The named next add-ons — Gatekeeper, Vault, Calico, Crossplane — are the obvious follow-on, and the request channel for unsupported CRDs suggests the list is meant to keep growing. Expect Klaudia's analysis to start covering add-on resources now that they are modelled rather than inspected by hand.