-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
🌱 Add fsnotify watcher+polling #3050
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vincepri The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
83cff1b
to
d27a3e1
Compare
Signed-off-by: Vince Prignano <[email protected]>
d27a3e1
to
814f289
Compare
Thx! /lgtm /hold I also opened cherry-pick PRs: |
LGTM label has been added. Git tree hash: e7a11ee4ce9104ed2ba2a5277bebca01c13f1d2f
|
This PR adds fsnotify back to the cert-watcher.
This helps in cases where fsnotify works and that depend on an instant certificate reload.
For example if the webhook certificate is directly used as caBundle in MutatingWebhookConfigurations / ValidatingWebhookConfigurations / CRDs.
Please note: It is highly recommended to use a CA (that is used as caBundle in MutatingWebhookConfigurations / ValidatingWebhookConfigurations / CRDs) and a separate serving certificate using that CA. So during serving cert rotation both the old and new certificate are valid. In that case fsnotify is not required and a cert reload within 10 seconds is good enough.