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

Multipath KUBCONFIG env variable is not supported #1

Closed
ggenot opened this issue Jan 17, 2019 · 5 comments · Fixed by #3
Closed

Multipath KUBCONFIG env variable is not supported #1

ggenot opened this issue Jan 17, 2019 · 5 comments · Fixed by #3

Comments

@ggenot
Copy link

ggenot commented Jan 17, 2019

if kubeConfigPath := os.Getenv("KUBECONFIG"); kubeConfigPath != "" {

Hello,
I use Multiple path in my KUBECONFIG env var as explaind in the doc

However the plugin try to "stat" the config file and fail as it expect a single file:

2019/01/17 13:00:55 getting tiller storage
2019/01/17 13:00:55 stat /home/ggenot/.kube/config-1:/home/ggenot/.kube/config-2:/home/ggenot/.kube/config-3:: no such file or directory
Error: plugin "backup" exited with error

Note that I redacted config name ;)

@maorfr
Copy link
Owner

maorfr commented Jan 17, 2019

Hey,

Thanks for bringing this up.
Seems like a pretty straight forward fix. I can do it in a couole of weeks myself (on vacation), or you can get involved and do it ;)

What do you say?

@mumrau
Copy link

mumrau commented Apr 8, 2019

Just wondering if there is a status about this issue?
No pressure at all by the way, it's still easy to make it work with a little export trickery, and the behavior ends up being as expected.

@maorfr
Copy link
Owner

maorfr commented Apr 8, 2019

waiting for someone to pick this up :)

@hickeyma
Copy link
Collaborator

@maorfr I can take this if that's ok?

@maorfr
Copy link
Owner

maorfr commented Jan 21, 2020

of course @hickeyma, thank yoU!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants