Operator panels · New in v0.3.0

Typed panels for the operators you actually run

PodSteer renders the custom resources you most likely run as purpose-built panels, not raw YAML: cert-manager Certificates with an expiry verdict, KEDA ScaledObjects, External Secrets, Argo Rollouts with promote and abort, Trivy reports, Karpenter NodePools, Gateway API routes and more. There is nothing to install; a panel appears when its API is in your cluster.

Download PodSteer All features

What is covered

  • GitOps: Argo CD Application, Flux Kustomization and HelmRelease.
  • cert-manager Certificate — including whether a renewal is overdue.
  • KEDA ScaledObject, with credential-looking trigger values redacted.
  • External Secrets ExternalSecret — keys mapped, no values read.
  • Argo Rollouts Rollout, with promote and abort behind the production gate.
  • Trivy Operator VulnerabilityReport.
  • Karpenter NodePool and NodeClaim.
  • Gateway API: GatewayClass, Gateway, HTTPRoute and GRPCRoute, with each parent's own verdict.
  • Dynamic Resource Allocation: ResourceClaim, ResourceClaimTemplate and DeviceClass.
  • Validating and Mutating admission policies and their bindings.
  • Gang scheduling: Workload and PodGroup (scheduling.k8s.io/v1beta1), with a link from a pod to its pod group.
A Trivy VulnerabilityReport for the checkout workload in storefront, open as a typed panel: counts by severity, the image nginx:1.27-alpine, a note that five other workloads in the namespace run the same image, the scanner and when it scanned, and the first vulnerabilities with the package versions that fix them. A Trivy VulnerabilityReport for the checkout workload in storefront, open as a typed panel: counts by severity, the image nginx:1.27-alpine, a note that five other workloads in the namespace run the same image, the scanner and when it scanned, and the first vulnerabilities with the package versions that fix them.
A Trivy report, read as a panel. Severities, the image and the fixed versions, and how many other workloads run the same image.

Built in, instead of a plugin API

A plugin surface is a compatibility promise owed for ever, and extension ecosystems in this category have broken under their users more than once. PodSteer ships typed panels for the controllers people actually run instead, and adding another is a change to PodSteer rather than something you install and keep working.

Everything else is still browsable: any custom resource is listed with the columns its own definition prints, with no code written for it.

Be honest

What it does not do.

  • There is no plugin or extension API, by decision.
  • The panels quote what each controller reports; only a Certificate's expiry is judged against the clock.
  • Karpenter's provider node classes, such as EC2NodeClass, are not covered.
  • Workload and PodGroup need Kubernetes 1.37 with the GenericWorkload feature gate on; without it there is nothing to show.

Read next

GitOps: Argo CD and Flux

Typed panels for Argo CD Applications and Flux Kustomizations and HelmReleases, and a warning before any change a controller will undo.

Security and RBAC

Privileges a spec takes, vulnerabilities your scanner already found, and what an account can actually do — answered by the API server.

Helm releases

Every Helm release and revision, listed from labels alone; one revision's values and manifest read only when you ask.

Compared with other tools: PodSteer vs Freelens · PodSteer vs Lens Desktop · PodSteer vs Headlamp