-
Notifications
You must be signed in to change notification settings - Fork 61
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
Fix nats-server-config-reloader for k8s secrets #131
Conversation
Thanks so much for the report and the fix!! 🙏 I will make a release with this change next week. |
Fixes nats-io#130 To fix this issue, the commit ensures that when a file is deleted, the Inotify watches immediately unregister it and then attempt to periodically re-register the file every second until the operation succeeds. This guarantees that the file will continue to be monitored reliably even after deletion.
* services: reload certificates when it is changed Hub stopped working because of expired mTLS certificates, even though the certs were correctly auto-rotated in the k8s cluster. * charts: set cert-manager.io/private-key-rotation-policy to ingress * charts: rotate mongo certificates when it has been changed * nats-server-config-reloader: expose plgd image until fix accepted nats-io/nack#131
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.
Thanks for this! Looks great save for few nits.
Co-authored-by: Piotr Piotrowski <piotrpiotrowski94@gmail.com>
Sure. We utilize |
Fixes #130
To fix this issue, the commit ensures that when a file is deleted, the Inotify watches immediately unregister it and then attempt to periodically re-register the file every second until the operation succeeds. This guarantees that the file will continue to be monitored reliably even after deletion.