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

registries.yaml environment variables for username and password #1685

Closed
saulfrank opened this issue Apr 25, 2020 · 2 comments
Closed

registries.yaml environment variables for username and password #1685

saulfrank opened this issue Apr 25, 2020 · 2 comments
Labels
kind/enhancement An improvement to existing functionality

Comments

@saulfrank
Copy link

saulfrank commented Apr 25, 2020

Is there a way to use environment variables for the registries.yaml file? It feels insecure to save plain text username and passwords on disk.

https://rancher.com/docs/k3s/latest/en/installation/private-registry/

How K8s does it:
https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/

@brandond
Copy link
Contributor

brandond commented Oct 20, 2020

K3s is is K8s. You are welcome to use image pull secrets if you want, they work just fine. Some users prefer to configure registries (endpoints, credentials) on the node itself in the container runtime config so that they are used globally, instead of having to inject them into every pod spec.

Even if we allowed storing credentials in environment variables... you would still have to define the variable contents somewhere - in the systemd unit or env file. I don't see how simply moving them from one file to another would make things any more secure. Do you have a proposal for how this might work that wouldn't just result in their being somewhere else on disk?

@brandond brandond removed their assignment Nov 7, 2020
@brandond brandond added kind/feature A large new piece of functionality kind/enhancement An improvement to existing functionality and removed kind/feature A large new piece of functionality labels Nov 7, 2020
@davidnuzik davidnuzik added this to To Triage in Development [DEPRECATED] via automation Feb 20, 2021
@caroline-suse-rancher
Copy link
Contributor

Closing as this is something we're considering a solution to in the Backlog

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement An improvement to existing functionality
Projects
Archived in project
Development

No branches or pull requests

4 participants