-
Notifications
You must be signed in to change notification settings - Fork 6
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
allow forcing a new ssh key pair #21
Comments
Please make it somehow automaticly regenerate certificate if it fails to use already existing. My current workaround is to add |
@Hronom What is the reason that the existing key fails? There is already logic for refreshing if the cert is no longer valid, so I'm wondering what the other failure modes are. |
@dafydd-t hello, I'm using version
If I restart containers it starting to work. Is it fixed in |
@Hronom 0.0.14 introduces some retries for the key signing request. This helps in some cases, but we've also identified a change required internally. That should get sorted in the next day or two. |
Thanks @dafydd-t , just a side note, we found this approach ( |
Currently the pdc-agent uses an existing SSH key pair and certificate if they exist and are valid. We should allow users to force a new ssh key pair and certificate to be generated.
Implement a
--force-key-file-overwrite
flag that generates a new SSH key pair and requests a new certificate using the new public key.The text was updated successfully, but these errors were encountered: