Galsza commented on PR #3972: URL: https://github.com/apache/ozone/pull/3972#issuecomment-1337520063
> @Galsza Thanks for the work. > > I was just wondering, is it also an option to add this feature as a daemon service in SCM, so that we don't have to do the cleaning manually? @symious Thanks for the comment. This is more of a housekeeping tool for older certificates. There is no need to add this feature as a daemon in SCM. The current plan for certificate rotation is that whenever a certificate is about the expire a new one will be created. This new certificate is used after instead of the old one. After some propagation time, when we can finally ensure that the old certificate is successfully replaced everywhere by the new one, the old certificate can be safely removed, which would be done there. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
