-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with k8s.io/docs/tasks/configure-pod-container/pull-image-private-registry/ #14615
Comments
@agemooij - thanks for this suggestion. Sounds like a good idea! |
/language en |
/kind feature |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
/priority backlog |
Did PR #14669 cover this by providing a helpful link? |
@sftim yes, that's great. Thanks! |
Problem:
The "Pull an Image from a Private Registry" page does not mention the fact that image pull secrets can be specified through a service account. This has lead many of my colleagues to the conclusion that the only way to use custom image pull credentials is through direct modification of all pods being deployed.
Searching Google on image pull secrets only brings up this page but almost never brings up the page that contains the relevant documentation, e.g. the page on how to how to add image pull secrets to a service account.
Proposed Solution:
The "Pull an Image from a Private Registry" page should have an extra section at the bottom of this page that either copies or references the documentation on how to add image pull secrets to a service account. A simple reference to the possibility and a link to the relevant doc would already help a great deal.
Page to Update:
https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
Kubernetes Version:
All current versions
The text was updated successfully, but these errors were encountered: