Skip to content

Support on-demand certificate reload on SIGHUP #88

Draft
AntiD2ta wants to merge 9 commits intocertificate-san-supportfrom
sighup-cert-renewal
Draft

Support on-demand certificate reload on SIGHUP #88
AntiD2ta wants to merge 9 commits intocertificate-san-supportfrom
sighup-cert-renewal

Conversation

@AntiD2ta
Copy link
Contributor

@AntiD2ta AntiD2ta commented Dec 10, 2025

This PR provides an alternative implementation of #83 to support on-demand certificate reload on a SIGHUP signal.

The PR's branch is based on #87, therefore it is suggested to merge that PR first and then update this PR's reference to point to master.

The GetCertificate function is designed to be a callback used by the Go standard library's tls.Config. This means it only runs when a client connects to the server and initiates a TLS handshake. Currently, a certificate reload is automatically attempted when GetCertificate is called if the current certificate is expired. We can keep this behavior or only allow a certificate reload after a SIGHUP.

Current tests are asserting the reloading behavior, but not Dirk's process reaction on a SIGHUP.

AntiD2ta and others added 2 commits December 10, 2025 14:15
Added new certmanager service

Co-authored-by:  Jacob Shufro <jacob@shuf.ro>
Updates:
- Add test to assert new certificates renewal feature
- Update test suite to use certManager to handle certificates

Co-authored-by:  Jacob Shufro <jacob@shuf.ro>
@AntiD2ta AntiD2ta self-assigned this Dec 10, 2025
- Bump ReleaseVersion to 1.2.1-rc.2
- Modify CA certificate handling to log a warning when no CA certificate is specified, allowing the use of standard CA certificates.
- Fix conditional check in parameter parsing to ensure correct application of parameters.
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

Successfully merging this pull request may close these issues.

1 participant