Move Docker credentials import to task documentation#12668
Conversation
|
Deploy preview for kubernetes-io-master-staging ready! Built with commit 70d6577 https://deploy-preview-12668--kubernetes-io-master-staging.netlify.com |
| If you need access to multiple registries, you can create one secret for each registry. | ||
| Kubelet will merge any `imagePullSecrets` into a single virtual `.docker/config.json` | ||
| when pulling images for your Pods. | ||
| If you already have a Docker credentials file, you can import this instead, |
There was a problem hiding this comment.
This isn't quite a complete sentence. Can you please explain how someone could import a Docker credentials file?
There was a problem hiding this comment.
Oops, wrong punctuation.
| type: kubernetes.io/dockerconfigjson | ||
| ``` | ||
|
|
||
| If you get the error message `error: no objects passed to create`, it may mean the base64 encoded string is invalid. |
There was a problem hiding this comment.
Credit to a0fb30a on that one. I'm really just editing what's already there.
|
/assign @thockin |
|
@thockin could you please review the updated content for technical accuracy. |
|
/tech review |
87c83b2 to
70d6577
Compare
|
Can we please assign to someone else. I am swamped right now.
…On Mon, Feb 18, 2019 at 5:45 AM Tim Bannister ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In
content/en/docs/tasks/configure-pod-container/pull-image-private-registry.md
<#12668 (comment)>:
> +- set `type` to `kubernetes.io/dockerconfigjson` <http://kubernetes.io/dockerconfigjson>
+
+Example:
+
+```yaml
+apiVersion: v1
+kind: Secret
+metadata:
+ name: myregistrykey
+ namespace: awesomeapps
+data:
+ .dockerconfigjson: UmVhbGx5IHJlYWxseSByZWVlZWVlZWVlZWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWxsbGxsbGxsbGxsbGxsbGxsbGxsbGxsbGxsbGxsbGx5eXl5eXl5eXl5eXl5eXl5eXl5eSBsbGxsbGxsbGxsbGxsbG9vb29vb29vb29vb29vb29vb29vb29vb29vb25ubm5ubm5ubm5ubm5ubm5ubm5ubm5ubmdnZ2dnZ2dnZ2dnZ2dnZ2dnZ2cgYXV0aCBrZXlzCg==
+type: kubernetes.io/dockerconfigjson
+```
+
+If you get the error message `error: no objects passed to create`, it may mean the base64 encoded string is invalid.
Credit to f0cd49a
<f0cd49a>
on that one. I'm really just editing what's already there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12668 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFVgVJzr_JvX-SJr185e9K0jtIfGMyLaks5vOq5cgaJpZM4a_CPC>
.
|
|
/unassign @thockin |
|
/assign @zparnold |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: zparnold The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* Move docker credentials import to task documentation Relevant to kubernetes#12072 * Call out helpful note about per-namespace secrets
* Move docker credentials import to task documentation Relevant to kubernetes#12072 * Call out helpful note about per-namespace secrets
* Move docker credentials import to task documentation Relevant to kubernetes#12072 * Call out helpful note about per-namespace secrets
This change makes sure that the information about pulling from multiple registries is still available in https://kubernetes.io/docs/concepts/containers/images/ (by hyperlinking to its new home).
The text about configuring multiple registries moves into https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
This explanation is task-oriented and is useful to readers who are already familiar with:
as isolated concepts.