fix(pgbouncer): avoid infinite pgbouncer pod delete cycle#29
Open
jwnx wants to merge 1 commit intoflyio-2.6.0from
Open
fix(pgbouncer): avoid infinite pgbouncer pod delete cycle#29jwnx wants to merge 1 commit intoflyio-2.6.0from
jwnx wants to merge 1 commit intoflyio-2.6.0from
Conversation
This patch changes the mechanism we use to ensure pgbouncers are rescheduled after a leadership change: instead of individually deleting pods, we change a label in pgbouncer deployment spec, forcing Kubernetes to replace the pods itself. It's the same mechanism we use to ensure repo-host has up-to-date secrets. Signed-off-by: Juliana Oliveira <juliana@fly.io>
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
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.
This patch changes the mechanism we use to ensure pgbouncers are
rescheduled after a leadership change: instead of individually deleting
pods, we change a label in pgbouncer deployment spec, forcing Kubernetes
to replace the pods itself. It's the same mechanism we use to ensure
repo-host has up-to-date secrets.
Signed-off-by: Juliana Oliveira juliana@fly.io