Kubernetes v1.6 [alpha]
This page provides an overview of PodPresets, which are objects for injecting certain information into pods at creation time. The information can include secrets, volumes, volume mounts, and environment variables.
Understanding Pod presets
A PodPreset is an API resource for injecting additional runtime requirements into a Pod at creation time. You use label selectors to specify the Pods to which a given PodPreset applies.
Using a PodPreset allows pod template authors to not have to explicitly provide all information for every pod. This way, authors of pod templates consuming a specific service do not need to know all the details about that service.
Enable PodPreset in your cluster
In order to use Pod presets in your cluster you must ensure the following:
You have enabled the API type
settings.k8s.io/v1alpha1/podpreset. For example, this can be done by including
--runtime-configoption for the API server. In minikube add this flag
--extra-config=apiserver.runtime-config=settings.k8s.io/v1alpha1=truewhile starting the cluster.
You have enabled the admission controller
PodPreset. One way to doing this is to include
--enable-admission-pluginsoption value specified for the API server. In minikube, add this flag
while starting the cluster.
How it works
Kubernetes provides an admission controller (
PodPreset) which, when enabled,
applies Pod Presets to incoming pod creation requests.
When a pod creation request occurs, the system does the following:
- Retrieve all
PodPresetsavailable for use.
- Check if the label selectors of any
PodPresetmatches the labels on the pod being created.
- Attempt to merge the various resources defined by the
PodPresetinto the Pod being created.
- On error, throw an event documenting the merge error on the pod, and create
the pod without any injected resources from the
- Annotate the resulting modified Pod spec to indicate that it has been
modified by a
PodPreset. The annotation is of the form
podpreset.admission.kubernetes.io/podpreset-<pod-preset name>: "<resource version>".
Each Pod can be matched by zero or more Pod Presets; and each
PodPreset can be
applied to zero or more pods. When a
PodPreset is applied to one or more
Pods, Kubernetes modifies the Pod Spec. For changes to
VolumeMounts, Kubernetes modifies the container spec for all containers in
the Pod; for changes to
Volume, Kubernetes modifies the Pod Spec.
Note: A Pod Preset is capable of modifying the following fields in a Pod spec when appropriate: - The
.spec.containersfield. - The
initContainersfield (requires Kubernetes version 1.14.0 or later).
Disable Pod Preset for a Specific Pod
There may be instances where you wish for a Pod to not be altered by any Pod
Preset mutations. In these cases, you can add an annotation in the Pod Spec
of the form:
For more information about the background, see the design proposal for PodPreset.
Was this page helpful?
Thanks for the feedback. If you have a specific, answerable question about how to use Kubernetes, ask it on Stack Overflow. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement.