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.
aws-secret-operator has deadlock occurs when rolling updating.
Details
In the
leader.Become
function, the operator waits until it becomes the leader.After that, Operator is create the file
/tmp/operator-sdk-ready
withready.NewFileReady()
.Rolling update
In the case of the rolling update, it works as follows.
leader.Become
function./tmp/operator-sdk-ready
is will be not created/tmp/operator-sdk-ready
This issue is the same as reported in the operator-sdk issue.
operator-framework/operator-sdk#920
operator-sdk fixes this bug in v0.4.0 release.
https://github.com/operator-framework/operator-sdk/releases/tag/v0.4.0
This bug fix removes the readiness check.
I include the same bug fix into aws-secret-operator.
logs