Skip to content
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

Enabling hot reloading of TLS certs #437

Open
thinkingfish opened this issue Jun 11, 2022 · 0 comments
Open

Enabling hot reloading of TLS certs #437

thinkingfish opened this issue Jun 11, 2022 · 0 comments

Comments

@thinkingfish
Copy link
Contributor

thinkingfish commented Jun 11, 2022

Is your feature request related to a problem? Please describe.
It is common to require TLS certs to be refreshed either periodically or on demand when previous certs, e.g. when secrets were leaked. Currently, a reboot is needed to pick up new certs in Pelikan-segcache. This means cert renewal gets in the way of upholding data availability.

Describe the solution you'd like
Many services that support TLS also support hot loading, which is the practice of (re-)loading certs and recreating the SSL context. Two general approaches can be considered: 1. periodic, on a timer predetermined at application start time; 2. on-demand, e.g. when a specific signal is received by the process. For feature parity with existing internal service, we should at least deliver 1.

Additional context
We should look at existing implementation when adding this feature to Pelikan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant