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

Move vsphere credentials from the Spec to k8s secrets #141

Closed
sidharthsurana opened this issue Dec 3, 2018 · 2 comments
Closed

Move vsphere credentials from the Spec to k8s secrets #141

sidharthsurana opened this issue Dec 3, 2018 · 2 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@sidharthsurana
Copy link
Contributor

Currently, the vsphere credentials are part of the Spec definition in plain text which is a huge security gap.
We need to move the credentials into k8s secrets to make a bit secure.

@sidharthsurana sidharthsurana self-assigned this Dec 3, 2018
@frapposelli
Copy link
Member

frapposelli commented Feb 1, 2019

/priority important-longterm
/kind feature

@k8s-ci-robot k8s-ci-robot added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Feb 1, 2019
@frapposelli frapposelli added this to the Next milestone Feb 1, 2019
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 1, 2019
@sflxn
Copy link

sflxn commented Feb 1, 2019

@sidharthsurana This is a duplicate of issue #9. Let's keep that issue and close this one since there are already some people on that issue and any updates we do there will ping them.

@sflxn sflxn closed this as completed Feb 1, 2019
jayunit100 pushed a commit to jayunit100/cluster-api-provider-vsphere that referenced this issue Feb 26, 2020
Signed-off-by: Vince Prignano <vince@vincepri.com>
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

No branches or pull requests

4 participants