Validator | Add validator to avoid changes to certain fields #13

New Issue

2026-05-27T20:53:18+02:00

t.behrendt commented

2026-05-27 20:53:18 +02:00

Certain fields cannot be removed on the resource, because the controller will not be able to reconcile the new status with Authentik.
These are e.g. the outpost field of a ProxyProvider. When this value gets update, the controller only gets the new state, not the old state.
We would have to iterate through all outposts to remove the provide. And that every time we handle the resource, as we don't know if the field got updated.

Instead, through a validator, we prevent that outpost field can be updated at all. Instead, we require the user to delete the resource first and create a new one. Similar to how this is handled with PVs.

Certain fields cannot be removed on the resource, because the controller will not be able to reconcile the new status with Authentik. These are e.g. the outpost field of a ProxyProvider. When this value gets update, the controller only gets the new state, not the old state. We would have to iterate through all outposts to remove the provide. And that every time we handle the resource, as we don't know if the field got updated. Instead, through a validator, we prevent that outpost field can be updated at all. Instead, we require the user to delete the resource first and create a new one. Similar to how this is handled with PVs.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: t.behrendt/authentik-kubernetes-operator#13