Feature: K8s Native

CRD-based.

Overview

Kubernetes-native means CRDs, operators, and admission controllers are the primary integration surface. Nova configuration lives in custom resources, an operator manages installation and lifecycle, kubectl is the operator's interface, and Kubernetes RBAC governs access. The discipline is matching the platform's idioms instead of grafting a separate control plane onto every cluster.

• CRD-based configuration. Nova config lives as Custom Resources, validated by the API server. Same review and versioning workflow as every other Kubernetes object.
• Operator-based deployment. An operator manages install, upgrades, scale, healing. Components self-manage between releases.
• kubectl-driven workflow. Operators interact via the same kubectl they already use. No new CLI to learn.
• GitOps and RBAC by default. CRDs flow through Argo CD and Flux; access governed by existing Kubernetes RBAC. Security model and deployment workflow both inherited.

The approach

Single-line operator install, CRDs as the source of truth, native Kubernetes status surfaces. Five idioms cover most operational use of the K8s integration; together they make Nova feel native instead of foreign.

• Operator install. One-line install via Helm or kubectl apply. Matches Kubernetes norms; no operator-specific bootstrap.
• CRD as source of truth. Configuration lives in CRDs, not in a separate API or web UI. Declarative config, reviewable diffs.
• Standard kubectl describe and get for status. Same commands operators already use. Muscle memory transfers.
• Lifecycle events plus per-field CRD reference. Kubernetes events surface state transitions; per-field CRD documentation supports self-service configuration.

Why this compounds

Each Kubernetes-using customer adopts via familiar patterns and goes from kubectl apply to working in minutes rather than hours. Self-managing components reduce operational burden over time, and every install teaches the team how to make the next one easier.

• Faster adoption. K8s teams adopt without learning new patterns. Time-to-value drops.
• GitOps-compatible. Argo CD and Flux pick up CRDs naturally. Modern deployment workflows just work.
• Self-managing components. Operator handles upgrades, scale, and healing. Operational burden drops.
• Year-one investment, year-two habit. First install pattern is the investment; subsequent ones run on autopilot.