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

Recognize early when an autocluster is started without an SSH agent #367

Open
celskeggs opened this issue Mar 11, 2019 · 3 comments
Open

Comments

@celskeggs
Copy link
Member

When the spire virt auto cluster command runs, it requires that an SSH agent exist for it to register SSH keys with -- but it doesn't check this until it's in the middle of configuring the supervisor node. If someone has forgotten to set one up, this means they need to re-run half of the process, which is very much a waste of time.

We should recognize the lack of an SSH agent immediately, possibly just by running ssh-add -l or recognizing whether the $SSH_AUTH_SOCK environment variable exists. This will save time.

@celskeggs
Copy link
Member Author

Relatedly, there's also a problem where, if the SSH agent has too many already-loaded identities, it can fail to authenticate because it runs out of tries. It may be worth clearing out old ssh identities from the SSH agent automatically, which might be part of the same fix. (Or could be a separate fix. Either way is good.)

@cryslith
Copy link
Member

cryslith commented May 1, 2019

@celskeggs
Copy link
Member Author

@dihernandez @krawthekrow any progress on this?

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

No branches or pull requests

4 participants