Catalog administration and revisions

The customer-facing overview explains why the catalog exists. This page documents operator surfaces that mutate catalog data and how those mutations reach clusters.

Kubernetes applications API

Operator or administrator roles can manage catalog application definitions:

• List / create / update / delete application rows (modern listings typically filter to current versioned rows only).
• Attach metadata and deployment rules JSON defining when an application applies (pre/post compute, workspace filters, visibility).

Customers do not call these routes unless your operator delegates self-service catalog (uncommon).

Revisions

A separate surface stores immutable release snapshots (Helm values, raw YAML, references). Each revision is frozen once published; applications pin an active revision pointer.

Deployments

Per-workspace (or per-cluster) install records track state, last error, and which revision was applied. Workspace provisioning and reconciliation read these records to keep desired add-ons healthy.

Kubernetes version catalog

System routes maintain the supported matrix for tenant workspace creation. Only active versions appear in customer create validators.

Related reading

• Kubernetes applications overview
• Kubernetes provisioning
• Reconciliation
• Technical verification