[Bug Fix] Handle TargetGroupBinding's networking changed from non-nil to nil #1510
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.
Handle TargetGroupBinding's networking changed from non-nil to nil
Bug:
When TargetGroupBinding's networking changed from non-nil to nil, e.g. changed the Ingress securityGroup from managed to
unmanaged, the securityGroup rule clean up will not happen in-time. (it eventually cleanup when other TargetGroupBinding reconciles)
Changes:
TargetGroupBinding
Upgrade controller-runtime to v0.6.3