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
I could not find a solution in the existing issues, docs, nor discussions.
Describe the bug
The PRs #1230 and #1232 have introduced hot reloading of the key stores to allow key rotation without downtimes. Unfortunately, it has been forgotten to update the implementation related to the exposure of certificate expiration metrics. This way, even if the certificates have been rotated, the expiration information of old certificates is still exposed.
How can the bug be reproduced
Start heimdall e.g. in decision with TLS enabled and metrics exposed
Check the certificate expiration metrics
Updated the key store used for TLS with a new key material and certificate
Check the certificate expiration metrics. It is the old one
Relevant log output
No response
Relevant configuration
No response
Version
v0.14.3-alpha
On which operating system are you observing this issue?
Linux
In which environment are you deploying?
Docker
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Preflight checklist
Describe the bug
The PRs #1230 and #1232 have introduced hot reloading of the key stores to allow key rotation without downtimes. Unfortunately, it has been forgotten to update the implementation related to the exposure of certificate expiration metrics. This way, even if the certificates have been rotated, the expiration information of old certificates is still exposed.
How can the bug be reproduced
Relevant log output
No response
Relevant configuration
No response
Version
v0.14.3-alpha
On which operating system are you observing this issue?
Linux
In which environment are you deploying?
Docker
Additional Context
No response
The text was updated successfully, but these errors were encountered: