Automate reloading of denylist #7
Description
To reload the list of credential IDs that should be denied, a restart of the authorizer is required. This may not be ideal and adds operational complexity.
Furthermore, recreation of pods doesn't automatically happen when a mutable configuration map is updated in Kubernetes.
Before adding this type of "hot reloading" feature, consider how it will affect service reliability, request latency (don't try to reload the list on each request) and avoid including new third-party dependencies (increased supply chain risks). A simple timer that checks modification date of the certificate/private key may be enough. Utilizing fsnotify/inotify could also be an option, but may require introduction of new dependencies.