whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Only one word typo fix (#15617)

Browse Source 
* Fix typo

* Fix typo

* Cange back to "will"
This commit is contained in:
Kobayashi Daisuke
2019-08-06 09:25:54 +09:00
committed by Kubernetes Prow Robot
parent da9db0b0c4
commit 97297af5ef
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/containers/images.md
+2 -2
View File
@@ -70,7 +70,7 @@ Credentials can be provided in several ways:
- Configuring Nodes to Authenticate to a Private Registry - Configuring Nodes to Authenticate to a Private Registry
- all pods can read any configured private registries - all pods can read any configured private registries
- requires node configuration by cluster administrator - requires node configuration by cluster administrator
- Pre-pulling Images - Pre-pulled Images
- all pods can use any images cached on a node - all pods can use any images cached on a node
- requires root access to all nodes to setup - requires root access to all nodes to setup
- Specifying ImagePullSecrets on a Pod - Specifying ImagePullSecrets on a Pod
@@ -243,7 +243,7 @@ template needs to include the `.docker/config.json` or mount a drive that contai
All pods will have read access to images in any private registry once private All pods will have read access to images in any private registry once private
registry keys are added to the `.docker/config.json`. registry keys are added to the `.docker/config.json`.
### Pre-pulling Images ### Pre-pulled Images
{{< note >}} {{< note >}}
If you are running on Google Kubernetes Engine, there will already be a `.dockercfg` on each node with credentials for Google Container Registry. You cannot use this approach. If you are running on Google Kubernetes Engine, there will already be a `.dockercfg` on each node with credentials for Google Container Registry. You cannot use this approach.