LoginSign Up
← Back to all sparks
K

Komodor

INFRA · APIS
Velocity0.0

Kubernetes operations and troubleshooting platform

komodor.com ↗

Komodor is extending its map of a cluster from native objects to the operators running on top of them.

kubernetesobservabilityoperators-crdsai-troubleshootinggitops
◆Current state
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.
◆Where it's heading
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.
◆Prediction
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.

◆Recent moves

  1. 2mo ago

    Gateway API resources are now visible in Komodor

    Gateway API resources — GatewayClasses, Gateways, HTTPRoutes, GRPCRoutes — become inspectable under the Network tab with the same configuration, status, and YAML view as native resources. It closes a coverage gap for teams who have moved off Ingress, and follows the add-ons work by three weeks.

    View source ↗
  2. 2mo ago

    Kubernetes Add-ons for Operator-Based Workloads

    ⚡ SPARK

    Operator-managed workloads become first-class resources: Komodor detects CRDs from a named list of ecosystems, surfaces health and runtime state, maps relationships, and routes them into Klaudia's root-cause analysis. It moves the platform's model of a cluster past what Kubernetes ships with, which is where most production infrastructure now lives.

    View source ↗
  3. 3mo ago

    Service Overview for Komodor Services

    Services get an Overview tab that leads with deployment status, recent activity, pod health, and reliability signals, replacing an Events landing tab that was often empty. It puts the assessment before the investigation, which matters most in the first thirty seconds of an incident.

    View source ↗
  4. 5mo ago

    Improved Navigation Experience Using Collapsable Sidebar

    The sidebar collapses to an icon-only mode for more screen space, with no change in functionality. Layout preference on a product whose views are dense.

    View source ↗
  5. 8mo ago

    Klaudia “Ask Me Anything” on Cluster & New Chat Experience

    Klaudia becomes invokable from any screen with a keyboard shortcut, scoped to a selected cluster, on top of a rebuilt chat with streaming responses. The assistant reaches further into the product without gaining new analytical ability — that comes from what the platform can model.

    View source ↗
  6. 8mo ago

    Instant Visibility Into Related Kubernetes Resources

    A Related Resources section on resource pages surfaces controllers, nodes, ConfigMaps, Secrets, HPAs, and Services connected to whatever is being investigated, with direct links. Relationship mapping at the object level — the same instinct that later produced the add-ons work at the ecosystem level.

    View source ↗