Status

The Status page shows the condition stream reported by the validator controller. Non-Ready states should be acted on.

The Status page displays the live condition stream from the CAT-BM Operator for this validator. It is the primary place to diagnose why a validator is not in a Ready state.

---

Status Cards

Three summary cards are shown at the top of the page:

Card	Description
Database	Whether the validator's database has been provisioned (e.g. Provisioned).
Auth provisioned	Whether the authentication configuration has been provisioned (e.g. Yes).
Observed generation	The resource generation number that the Operator most recently reconciled against.

The Observed generation value increments each time the Validator CR spec is updated. If the observed generation does not match the current resource version, the Operator may still be reconciling a recent change.

---

Conditions Table

Below the status cards, a table lists all conditions reported by the validator controller:

Column	Description
Type	The condition type (e.g. Ready).
Status	Whether the condition is currently true or false.
Reason	A machine-readable reason code for the current status (e.g. AllApplicationsReady).
Message	A human-readable description of the current state.
Last transition	The timestamp of the most recent status change for this condition.

Non-Ready states should be acted on. If the Ready condition shows False, check the Reason and Message columns for details, and refer to the Summary page to identify which component is unhealthy.

[TODO: document the full set of condition types and reason codes that can appear — e.g. conditions other than Ready, and non-AllApplicationsReady reason codes]