fix(backups): reloads repo-host when secrets are updated #23
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Juliana Oliveira <juliana@fly.io>
Signed-off-by: Juliana Oliveira <juliana@fly.io>
Signed-off-by: Juliana Oliveira <juliana@fly.io>
Signed-off-by: Juliana Oliveira <juliana@fly.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Repo-host mounts the latest certificates as secrets upon creation. Every now and then
these certificates are updated (expiry, corruption, race condition, etc) and if repo-host is
not restarted, pgbackrest jobs will fail due to file mismatch.
This patch introduces an annotation that tracks pgbackrest secret
resourceVersioninrepo-host, causing changes to the secret to trigger a repo-host restart and forcing it to
load the latest certificate file.
Signed-off-by: Juliana Oliveira juliana@fly.io