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§
- Status
Report - What one reconcile pass established.
available/exposedoverride the verdict derived from the Deployment/Service (a foreign object, or an apply that failed);tokensisNonewhen the pass did not observe tokens, and the previous status values are then kept. - Token
Facts - Token facts a pass observed after its writes.
- Verdict
- One condition’s status, reason and message.
Enums§
- Condition
Kind - The five conditions, in the order they are written.
- Truth
- Condition status.
Constants§
Functions§
- available_
verdict Available: the rollout is complete and every desired replica is available. A rollout in progress isFalseeven while old pods serve.- block_
verdict - The verdict for a block, on the condition it belongs to.
- build_
status - Build the full status. Pure:
nowis the transition time of a condition whose status changed. - exposed_
verdict Exposedand the endpoint clients should use.- is_
ready readyis true only when identity, configuration, availability and exposure are allTrue.Rotatingis informational.- kube_
time - Kanidm token time as a Kubernetes timestamp.
- patch_
status - Server-side apply the status with
forceunder our field manager. Returns whether a write was needed (an unchanged status is not written).