feat: daemonset maxsurge to prevent unavailability on config changes#819
Open
feat: daemonset maxsurge to prevent unavailability on config changes#819
Conversation
Member
Author
Release noteThe OPA DaemonSet now uses maxSurge=1 and maxUnavailable=0 for its rolling update strategy. During rolling updates (e.g. triggered by OPA config changes), a new OPA pod is created and must become ready before the old pod is terminated. This eliminates the brief availability gap that previously caused errors in products like Trino when the local OPA pod was unavailable during restarts. |
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.
Description
Solves the problem reported in #817
Set maxSurge=1 and maxUnavailable=0 on the OPA
DaemonSetso that during rolling updates, the new OPA pod is created and becomes ready before the old pod is terminated. This eliminates the availability gap that causes errors in products like Trino when OPA config changes trigger aDaemonSetrestart.DaemonSet
maxSurgegraduated to GA in Kubernetes 1.25, our current minimum supported Kubernetes version is 1.31.Definition of Done Checklist
Author
Reviewer
Acceptance
type/deprecationlabel & add to the deprecation scheduletype/experimentallabel & add to the experimental features tracker