-
Notifications
You must be signed in to change notification settings - Fork 261
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
issue internal CA for 20 years #319
Conversation
It deserves a comment in the commit message, otherwise OK for me. I believe it applies to the QEMU CA certificate too (qemu-ca.pem) but don't forget to check it in the verification. |
to repeat the title, why? Feel free to update
yes, it applies to QEMU CA too. |
007be6d
to
5537ea5
Compare
/ost |
No, to explain why we need to extend the certificate lifetime. If there is no reason then we don't need the change.
I think you can explain it best. |
|
5537ea5
to
f9b3258
Compare
Currently our internal CA is always issued for 10 years during the initial engine-setup. This carries over upgrades and on old enough installations we can get close to expiration. We don't have an easy way how to replace internal CA without complete downtime, and running over the expiration date leads to a complete cease of communication between all oVirt components. Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=2079799
f9b3258
to
23a5459
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=2079799