Use deployment strategy: Recreate for scheduler and websocket deployments to avoid coexisting replicas #318
Conversation
This file contains 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
modified: zammad/Chart.yaml
|
This is great @klml. We'd also need to apply this to the websocket server, can you please include it here? |
mgruner
approved these changes
Feb 6, 2025
mgruner
changed the title
|
👏 thanks a lot @klml! 🚀 |
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.
What this PR does / why we need it
Currently the scheduler is RollingUpdate (it is the default value). This leads to an small time period with 2 schedulers.
But the scheduler may only run once per cluster..
Changing deployment strategy to
Recreate DeploymentChecklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]