Custom Resources
The Kubernetes extension mechanism lets platforms and applications define their own API types. This section covers how Kuboard discovers, presents and manages CRDs (CustomResourceDefinition, Kubernetes Custom Resource Definitions) and their CR (Custom Resource) instances.
Quick Navigation
| Section | Content | When to Read |
|---|---|---|
| CRDs | Inspect registered CRDs: scope, versions and categories | See what extension APIs the cluster offers |
| Custom Resource Instances | List, create, edit and delete instances of a specific CRD | Day-to-day use of Operator or platform-driven CRDs |
Recommended Reading Order
- Survey cluster capabilities — open CRDs to see what is already registered and confirm the resource you need is available;
- Daily operations — move to the relevant CRD's Custom Resource Instances list to perform CRUD (Create, Read, Update, Delete) operations;
- Missing resources — if a CRD is installed in the cluster but not shown by Kuboard, it usually means the cache has not synced yet. Trigger a full sync or wait for the next cycle.
Auto-discovery
CRDs do not require manual menu registration: LoginServiceMenuLoader.populateCustomResourceMenu automatically builds the "Custom Resources" group in the left sidebar from any synchronized CRD. Common CRDs (Cert-Manager, Argo CD, Ingress-NGINX, etc.) usually appear within one sync cycle of installation.