Detections
Analytics
1.2.12 Ensure that the admission control plugin AlwaysPullImages is set
Warning! Audit Deprecated
This audit has been deprecated and will be removed in a future update.
View Next Audit VersionInformation
Always pull images.Rationale:
Setting admission control policy to AlwaysPullImages forces every new pod to pull the required images every time. In a multi-tenant cluster users can be assured that their private images can only be used by those who have the credentials to pull them. Without this admission control policy, once an image has been pulled to a node, any pod from any user can use it simply by knowing the image's name, without any authorization check against the image ownership. When this plug-in is enabled, images are always pulled prior to starting containers, which means valid credentials are required.
Impact:
Credentials would be required to pull the private images every time. Also, in trusted environments, this might increases load on network, registry, and decreases speed.
This setting could impact offline or isolated clusters, which have images pre-loaded and do not have access to a registry to pull in-use images. This setting is not appropriate for clusters which use this configuration.
Solution
Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml on the master node and set the --enable-admission-plugins parameter to include AlwaysPullImages.--enable-admission-plugins=...,AlwaysPullImages,...
Default Value:
By default, AlwaysPullImages is not set.
See Also
Item Details
Audit Name: CIS Kubernetes Benchmark v1.6.1 L1 Master
References: CSCv6|14.4, CSCv7|14.6
Plugin: Unix
Control ID: 0aa0cc83b0620d594474c0e3bec04231f2e0d21f6edc800f979414d70d4793b5