-
Notifications
You must be signed in to change notification settings - Fork 220
feat: add feature switch to use SSA for managing finalizer #2845
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: next
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a big fan of adding yet another flag to control SSA behavior…
yeah me neither TBH, would be better without but, this can be life saving in future. |
will work on a reproducer before I merge this |
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
1f09a47
to
70e8910
Compare
@@ -505,6 +504,18 @@ default boolean useSSAToPatchPrimaryResource() { | |||
return true; | |||
} | |||
|
|||
/** | |||
* Setting this to {@code true}, controllers will use SSA for adding finalizers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might help to document why it might be a good idea to set this to false, in particular point to the Kubernetes issue.
Discovered a weird bug (will describe more in detail later) when adding finalizer with SSA.
Therefore adding explicit feature switch for finalizer management (SSA / no SSA).
Would like to have a patch release with this, but for next minor release (5.2) would set this flag to
false
, so by defaultnot use SSA for finalizer managment.
Signed-off-by: Attila Mészáros a_meszaros@apple.com