Kubernetes Admission Controller Concepts: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=External= * https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/ =Internal= * Kubernetes_Control_Plane_and_Data_Plane_Concepts#Admission_Controlle...") |
|||
| Line 3: | Line 3: | ||
=Internal= | =Internal= | ||
* [[Kubernetes_Control_Plane_and_Data_Plane_Concepts#Admission_Controllers|Kubernetes Control Plane and Data Plane Concepts]] | * [[Kubernetes_Control_Plane_and_Data_Plane_Concepts#Admission_Controllers|Kubernetes Control Plane and Data Plane Concepts]] | ||
=Overview= | |||
An admission controller is a piece of code that intercepts requests to the Kubernetes API server prior to persistence of the metadata, but after the request is authenticated and authorized. | |||
=Admission Controller Types= | =Admission Controller Types= | ||
==AlwaysPullImages== | ==AlwaysPullImages== | ||
{{External|https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#alwayspullimages}} | {{External|https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#alwayspullimages}} | ||
Revision as of 01:02, 3 September 2020
External
Internal
Overview
An admission controller is a piece of code that intercepts requests to the Kubernetes API server prior to persistence of the metadata, but after the request is authenticated and authorized.