Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is Initializers part of the admission controller chain #32

Open
jianlongzhou opened this issue Mar 26, 2020 · 1 comment
Open

Is Initializers part of the admission controller chain #32

jianlongzhou opened this issue Mar 26, 2020 · 1 comment

Comments

@jianlongzhou
Copy link

From this doc document: https://v1-16.docs.kubernetes.io/docs/reference/access-authn-authz/admission-controllers/.

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.

@navaati
Copy link

navaati commented Apr 6, 2020

Hi.

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 :).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants