dashboard
Dashboard CRD, GVK: data.demo.inrun.dev/v1alpha1, Kind=Dashboard
Overview
dashboard is a custom resource managed by the
data-platform operator running on Inrun.
Resources of this type are namespace-scoped.
| Field | Value |
|---|---|
| API Version | data.demo.inrun.dev/v1alpha1 |
| Kind | Dashboard |
| GVR (plural) | data.demo.inrun.dev/v1alpha1, Resource=dashboards |
| Scope | Namespaced |
| Cross-read access |
✓ allowed — sibling operators may read this CRD's CR state via cross:
|
Reconcile Mode
This CRD runs in dynamic mode: Inrun works with the unstructured object, and no Go types are compiled in.
It is reconciled declaratively: the Blueprint's onCreate and onReconcile templates, with expressions like {{ .spec.field }}, become the CR's children and status.
Whatever the reconciler, the runtime owns the lifecycle: Inrun's finalizer, managed labels, applying and pruning children, events, metrics, health, and holding a deleted CR until its finalizing reconcile is done.
Configuration
The operator maintains 3 worker goroutines to process reconcile events concurrently. Each worker dequeues one CR key at a time, reconciles it, and returns. The queue has a maximum depth of 500 events.
Inrun resyncs all managed resources every 15s by re-enqueueing every CR key. This ensures drift caused by external changes is corrected even without a Kubernetes watch event.
Child Resources
When the operator reconciles a dashboard instance it creates and manages
the following Kubernetes resources on its behalf. These are owned by the CR via owner references
and are deleted automatically when the CR is deleted (unless deletion protection is active).
Resources listed under onCreate are created on the first reconcile. Resources listed under onReconcile are re-applied on every reconcile cycle. A resource appearing in both phases is created once and kept in sync thereafter.
| Kind | Count | Lifecycle phases |
|---|---|---|
ConfigMap |
1 | onCreate |
To see the actual child resources created for a running instance, navigate to the instance's detail page from the data-platform control panel.
operatorBox
Summary of the reconciler configuration declared in the Blueprint for this CRD.
| Feature | Configured | Detail |
|---|---|---|
| Hooks | — | No reconcile hooks |
| Constructor | — | None |
| Finalizers | 1 | inrun.dev/cleanup |
kubectl Reference
Use the commands below to interact with dashboard resources from the command line.
List resources
kubectl get dashboard -n <namespace>
Describe a resource
kubectl describe dashboard <name> -n <namespace>
Get YAML
kubectl get dashboard <name> -n <namespace> -o yaml
Watch for changes
kubectl get dashboard -n <namespace> -w
Delete a resource
kubectl delete dashboard <name> -n <namespace>
Filter by Inrun managed label
kubectl get dashboard -l inrun.dev/managed=true -n <namespace>
Access Control
The operator holds the following RBAC permissions to manage dashboard resources.
1 configmaps, 1 dashboards, 1 dashboards/status
| API Groups | Resources | Verbs |
|---|---|---|
data.demo.inrun.dev |
dashboards |
get list watch create update patch delete |
data.demo.inrun.dev |
dashboards/status |
get update patch |
core |
configmaps |
get list watch create update patch delete |
Endpoints
Inrun exposes per-CRD HTTP endpoints for health reporting and runtime introspection.
Endpoints can be selectively disabled in the Blueprint via endpoints:.
| Endpoint | Path | Status |
|---|---|---|
| Health | /blueprint/dashboard/health |
✓ enabled |
| Info | /blueprint/dashboard |
✓ enabled |
| CR List | /blueprint/dashboard/cr |
✓ enabled |