Conditions

Conditions are machine-readable status signals on Managed Objects that drive the computed object state. Model, severities, UI/API behaviour and state computation.

Conditions

Conditions are machine-readable status signals on Managed Objects. They drive the computed object state (OK / WARNING / CRITICAL) and are visible in the UI, API, filters and the Operations Dashboard.

Model

Layer Role
Condition Catalog entry (name, description, severity, system/custom)
ConditionInstance Active or resolved instance on a concrete object

The read source of truth is ConditionInstance. The older JSONField conditions on objects now only serves as a write sink for backwards compatibility and is no longer read for state/UI.

Severity

Severity Effect on object state
INFO Informational — state typically remains OK
WARNING Object degraded, still usable (often threshold-based)
CRITICAL Object not functional; often an immediate state change

Examples: certificate about to expire (WARNING), certificate expired (CRITICAL), missing backups, unhealthy loadbalancer deployments — see also LoadBalancer and Backup.

UI & API

  • Info drawer and Conditions tab read ConditionInstance
  • Table filter has_conditions is based on instances
  • Hover popover in the State column (V2 tables)
  • System conditions are maintained via seed and cannot be deleted by regular users

State computation

Object state is derived from active conditions. Mutations (add/remove condition) trigger a recompute; the full aggregate path does not run on every save(). During an ongoing reconciliation, duplicate recomputes are avoided.

Related topics