From 1c5188cc15140dd309d2d2d0f8f4756e07ca5d10 Mon Sep 17 00:00:00 2001 From: Shashank Patel Date: Fri, 5 Apr 2019 04:01:20 +0530 Subject: [PATCH] Fix typo in /docs/concepts/containers/images/ (#13628) Associated with #13627 --- content/en/docs/concepts/containers/images.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/containers/images.md b/content/en/docs/concepts/containers/images.md index 6f22211ced..de04645b9d 100644 --- a/content/en/docs/concepts/containers/images.md +++ b/content/en/docs/concepts/containers/images.md @@ -360,7 +360,7 @@ common use cases and suggested solutions. - Or, when on GCE/Google Kubernetes Engine, use the project's Google Container Registry. - It will work better with cluster autoscaling than manual node configuration. - Or, on a cluster where changing the node configuration is inconvenient, use `imagePullSecrets`. -1. Cluster with a proprietary images, a few of which require stricter access control. +1. Cluster with proprietary images, a few of which require stricter access control. - Ensure [AlwaysPullImages admission controller](/docs/reference/access-authn-authz/admission-controllers/#alwayspullimages) is active. Otherwise, all Pods potentially have access to all images. - Move sensitive data into a "Secret" resource, instead of packaging it in an image. 1. A multi-tenant cluster where each tenant needs own private registry.