Skip to content
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/ #12072

Closed
1 of 2 tasks
prary opened this issue Jan 4, 2019 · 4 comments
Closed
1 of 2 tasks
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@prary
Copy link
Contributor

prary commented Jan 4, 2019

This is a...

  • Feature Request
  • Bug Report

Problem:
I'll keep it short why are we authenticating twice once

  • docker login
  • kubectl create secret docker-registry regcred --docker-server= --docker-username= --docker-password= --docker-email=

Twice we have to use username and password, I think this extra step can be avoided.

Proposed Solution:
Use ~/.docker/config.json as secret to authenticate with registry?

Page to Update:
https://kubernetes.io/...

sftim added a commit to sftim/kubernetes-website that referenced this issue Feb 16, 2019
sftim added a commit to sftim/kubernetes-website that referenced this issue Feb 18, 2019
k8s-ci-robot pushed a commit that referenced this issue Feb 28, 2019
* Move docker credentials import to task documentation

Relevant to #12072

* Call out helpful note about per-namespace secrets
kwiesmueller pushed a commit to kwiesmueller/website that referenced this issue Feb 28, 2019
* Move docker credentials import to task documentation

Relevant to kubernetes#12072

* Call out helpful note about per-namespace secrets
krmayankk pushed a commit to krmayankk/kubernetes.github.io that referenced this issue Mar 11, 2019
* Move docker credentials import to task documentation

Relevant to kubernetes#12072

* Call out helpful note about per-namespace secrets
yagonobre pushed a commit to yagonobre/website that referenced this issue Mar 14, 2019
* Move docker credentials import to task documentation

Relevant to kubernetes#12072

* Call out helpful note about per-namespace secrets
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 4, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 4, 2019
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

3 participants