Add optional deployment annotations #251
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #250
Via annotations one can configure reloader to reload the related service whenever a change to a secret or configmap happens:
By default deployments will be reloaded whenever any secret/map mounted on them is changed. This can be configured with great granularity via annotations either in the deployment or secrets (you only want to reload whenever one particular secret changes, etc.). I think the default behaviour is good enough.
Via this strategy the server will reload whenever the policy package is updated, or daemons will reload whenever the certificate is updated by the cronjob.