Documentation menu

docs / working with resources

Custom Resources (CRDs)

Klustr discovers Custom Resource Definitions automatically — you don't configure anything. Any CRD on the cluster becomes browsable.

How discovery works

On connect, Klustr lists CustomResourceDefinition objects and groups them in the sidebar by API group, below the built-in resource groups. When you open a CR list view, Klustr lazily starts a watch for that specific resource, so subsequent list and detail reads come from the local cache rather than hitting the apiserver again. A brand-new CRD installed while you're connected shows up without a restart.

Browsing and editing

  • The generic CR list shows the objects for that kind.
  • The detail dialog shows YAML by default. A CR that one of the integrations below covers opens on that integration's overview instead, even from the generic list.
  • YAML edit, delete and (where applicable) scale work through the dynamic client, the same as built-in kinds — subject to a context's read-only mode.

Some CRDs get a first-class, typed UI instead of the generic YAML view when their API is detected:

  • Argo CD and Flux — see GitOps.
  • Tekton — PipelineRuns, TaskRuns, Pipelines and Tasks; see Tekton Pipelines.
  • Gateway API — see Gateway API.
  • Kyverno — policies, PolicyExceptions and the wgpolicyk8s.io policy reports; see Kyverno & policy reports.
  • cert-manager — Certificates, Issuers / ClusterIssuers and the full issuance chain (CertificateRequest → Order → Challenge), with ready/expiry status and a one-click Renew.
  • Istio — VirtualServices, DestinationRules and PeerAuthentications.
  • Karpenter — NodePools and NodeClaims with provisioning status, surfaced when the karpenter.sh CRDs are present, and the AWS provider's EC2NodeClasses.
  • Cilium — network policies, endpoints, nodes, identities, IP pools and BGP configuration; see Cilium.

Each integration reads its CRDs at the API version the cluster serves, so an older install, such as Karpenter before 1.0 or Flux before 2.3, works as well as a current one.

Everything else stays under the generic CRD browser — which is enough for most operators most of the time.