You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the key features of csi-lib is Automatically rotating/renewing certificates near expiry. But do we consider make this feature optional?
One particular use case is: one-time and short-lived cert for init-container (for mTLS to pull some secrets).
The user container will no longer need the cert after consuming it. Since the pod is still running, csi-lib will continue the renewal logic for this short-lived cert. With least privilege guidance, shall we disable the renewal in this case ?
Upon checking the code, all certificates will be auto renewed once it hits the NextIssuanceTime: https://github.com/cert-manager/csi-lib/blob/v0.3.0/manager/manager.go#L499
A workaround is to set the NextIssuanceTime much longer than the pod lifetime. But add an option here (pass in as volumeAttribute) would be much cleaner logic.
The text was updated successfully, but these errors were encountered:
One of the key features of
csi-lib
isAutomatically rotating/renewing certificates near expiry
.But do we consider make this feature optional?
One particular use case is: one-time and short-lived cert for init-container (for mTLS to pull some secrets).
The user container will no longer need the cert after consuming it. Since the pod is still running,
csi-lib
will continue the renewal logic for this short-lived cert. With least privilege guidance, shall we disable the renewal in this case ?Upon checking the code, all certificates will be auto renewed once it hits the
NextIssuanceTime
:https://github.com/cert-manager/csi-lib/blob/v0.3.0/manager/manager.go#L499
A workaround is to set the
NextIssuanceTime
much longer than the pod lifetime. But add an option here (pass in as volumeAttribute) would be much cleaner logic.The text was updated successfully, but these errors were encountered: