Skip to main content

Module controller

Module controller 

Source
Expand description

Controller wiring: watches, stores and the run entry point. KanidmRadiusServer controller wiring.

Owned objects (Deployments, Services, and config Secrets through a metadata-only watcher) trigger their owner. Referenced inputs carry no Kaniop label, so metadata-only watchers over all Secrets and ConfigMaps are mapped by namespace and name to the RADIUS servers that reference them; their data is never cached. Changes of a referenced Kanidm spec (origin, domain, image, namespace selector) trigger every RADIUS server pointing at it.

kube-runtime never runs two reconciles of the same object at once, which the token executors rely on: generate_api_token returns only the bearer and the new token id is found by listing before and after the mint.

Structs§

Context

Constants§

CONTROLLER_ID

Functions§

radius_for_config_map
RADIUS servers in namespace whose Kanidm CA is the ConfigMap name.
radius_for_kanidm
RADIUS servers whose kanidmRef resolves to namespace/name.
radius_for_secret
RADIUS servers in namespace that reference the Secret name (NAS shared secret, EAP TLS Secret, or a Secret-kind Kanidm CA).
run
Start the controller. Returns immediately (controller disabled) when the CRD is not installed.