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§
Constants§
Functions§
- radius_
for_ config_ map - RADIUS servers in
namespacewhose Kanidm CA is the ConfigMapname. - radius_
for_ kanidm - RADIUS servers whose
kanidmRefresolves tonamespace/name. - radius_
for_ secret - RADIUS servers in
namespacethat reference the Secretname(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.