You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An admission controller is a piece of code that intercepts requests to the Kubernetes API server prior to persistence of the object, but after the request is authenticated and authorized.
But this article says that
After an object is persisted to the datastore, it is not made fully visible by the apiserver or scheduled until a series of intializers have run.
The text was updated successfully, but these errors were encountered:
It seems Initializers were an Alpha concept and were abandoned in this form (see kubernetes/kubernetes#72972).
However, don't mourn them, because their functionality is provided by a special Admission Controller called "MutatingAdmissionWebhook" (see beginning of this paragraph) !
That way, instead of a new, different concept, it's unified with Admission Controllers and that's one less thing to know :).
From this doc document: https://v1-16.docs.kubernetes.io/docs/reference/access-authn-authz/admission-controllers/.
But this article says that
The text was updated successfully, but these errors were encountered: