Skip to main content

Module status

Module status 

Source
Expand description

Conditions and status, applied with server-side apply. Status of a KanidmRadiusServer: a pure builder plus the SSA write.

Status is a report and cache only. Every pass rebuilds it from what the pass established (StatusReport) and the live Deployment and Service. All five conditions are always emitted, keyed by type; a condition’s lastTransitionTime moves only when its status changes.

Structs§

StatusReport
What one reconcile pass established. available/exposed override the verdict derived from the Deployment/Service (a foreign object, or an apply that failed); tokens is None when the pass did not observe tokens, and the previous status values are then kept.
TokenFacts
Token facts a pass observed after its writes.
Verdict
One condition’s status, reason and message.

Enums§

ConditionKind
The five conditions, in the order they are written.
Truth
Condition status.

Constants§

TYPE_AVAILABLE
TYPE_CONFIGURATION_READY
TYPE_EXPOSED
TYPE_IDENTITY_READY
TYPE_ROTATING

Functions§

available_verdict
Available: the rollout is complete and every desired replica is available. A rollout in progress is False even while old pods serve.
block_verdict
The verdict for a block, on the condition it belongs to.
build_status
Build the full status. Pure: now is the transition time of a condition whose status changed.
exposed_verdict
Exposed and the endpoint clients should use.
is_ready
ready is true only when identity, configuration, availability and exposure are all True. Rotating is informational.
kube_time
Kanidm token time as a Kubernetes timestamp.
patch_status
Server-side apply the status with force under our field manager. Returns whether a write was needed (an unchanged status is not written).