Skip to content

fix: serialize SecurityGroup ingress reconciles per SecurityGroup - #4890

Open
madvocate wants to merge 1 commit into
kubernetes-sigs:mainfrom
madvocate:issue-4889
Open

fix: serialize SecurityGroup ingress reconciles per SecurityGroup#4890
madvocate wants to merge 1 commit into
kubernetes-sigs:mainfrom
madvocate:issue-4889

Conversation

@madvocate

@madvocate madvocate commented Aug 29, 2026

Copy link
Copy Markdown

Issue

#4889

Description

Checklist

  • Added tests that cover your change (if possible)
  • Added/modified documentation as required (such as the README.md, or the docs directory)
  • Manually tested
  • Made sure the title of the PR is a good description that can go into the release notes

BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯

  • Backfilled missing tests for code in same general area 🎉
  • Refactored something and made the world a better place 🌟

@kubernetes-prow kubernetes-prow Bot added the do-not-merge/invalid-commit-message Indicates that a PR should not merge because it has an invalid commit message. label Aug 29, 2026
@kubernetes-prow

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: madvocate
Once this PR has been reviewed and has the lgtm label, please assign oliviassss for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@linux-foundation-easycla

linux-foundation-easycla Bot commented Aug 29, 2026

Copy link
Copy Markdown

CLA Signed
The committers listed above are authorized under a signed CLA.

  • ✅ login: madvocate / name: Marek Suscak (b5b430b)

@kubernetes-prow

Copy link
Copy Markdown
Contributor

Welcome @madvocate!

It looks like this is your first PR to kubernetes-sigs/aws-load-balancer-controller 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/aws-load-balancer-controller has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@kubernetes-prow kubernetes-prow Bot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Aug 29, 2026
@kubernetes-prow

Copy link
Copy Markdown
Contributor

Hi @madvocate. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@kubernetes-prow kubernetes-prow Bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Aug 29, 2026
Concurrent reconciles of the same SecurityGroup each perform a
non-atomic read-modify-write sequence: fetch the current rules, diff
them against the desired permissions, then authorize/revoke. When two
reconciles interleave, one can diff against a snapshot taken while the
other was mid-mutation and revoke rules without granting replacements,
leaving the SecurityGroup without any of the controller-managed rules.

With the shared backend SecurityGroup feature this removes every
ALB-to-target ingress rule on the cluster SecurityGroup at once,
failing health checks and client traffic for all load balancers until
the deferred TargetGroupBinding reconciler restores the rules (~30
minutes after a controller restart).

Observed in production during Fargate maintenance: endpoint churn on
the TargetGroupBinding defining the aggregated port-range boundary
produced two concurrent reconciles; CloudTrail shows the controller
authorizing tcp/3000-3008, revoking tcp/3000-8025, then 45 seconds
later revoking tcp/3000-3008 again with no replacement grant.

Serialize ReconcileIngress per SecurityGroup ID with a keyed mutex held
across the fetch and the mutations, so every reconcile diffs against
post-mutation state. Reconciles of different SecurityGroups are not
serialized against each other.
@kubernetes-prow kubernetes-prow Bot removed the do-not-merge/invalid-commit-message Indicates that a PR should not merge because it has an invalid commit message. label Sep 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant