Generated at build time from
charts/racora-crds/README.md(helm-docs:values.yaml+README.md.gotmpl); edit the source, not this page.
racora-crds
CustomResourceDefinitions for Racora.
What this installs
| CRD | Kind | Short | Scope |
|---|---|---|---|
nrcells.racora.io | NRCell | cell | Namespaced |
subscribers.racora.io | Subscriber | sim | Namespaced |
An NRCell is a cell the controller brings up; a Subscriber is a SIM the
core controller provisions into the selected core provider. Both CRDs are
annotated helm.sh/resource-policy: keep so that
helm uninstall does NOT delete it. CRDs encode stable identity
that survives chart lifecycle; deletion is an explicit operator
action, never a chart side-effect.
Install
helm install racora-crds ./charts/racora-crds
CRDs are templated under templates/ (not crds/) so they DO upgrade
on helm upgrade. This is intentional — the crds/ directory only
installs once and never updates, which is the wrong behavior for an
actively-evolving API group like racora.io/v1alpha1.
Verify
kubectl get crd | grep racora.io
kubectl explain nrcell.spec
kubectl explain subscriber.spec
Ordering
This chart MUST install before:
racora-controller(consumes the NRCell CRD; its core controller the Subscriber CRD)racora-cu(cuip ServiceAccount + RBAC reference the CRD)- Any scenario NRCells
Nothing declares this as a dependency: within one release Helm's kind-sorted
apply puts the CRD ahead of the namespaced objects, and on the k3s platform
the installer applies the CRD out-of-band before the release exists
(crds.enabled=false).
What stays the same
The racora.io API group is the project's stable CRD group identifier.
It does NOT change when k8s namespaces are renamed — Racora is the project
name; namespaces are deployment topology.