NLB LoadBalancer doesn't update security groups about cloud-provider-aws

[selslack]

@ykzj This is about Security Groups for nodes, which are being applied/managed by k8s to support loadBalancerSourceRanges.

[ykzj]

NLB is not supporting security group now.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[selslack]

/remove-lifecycle stale

[adamrbennett]

I'm also facing this. Moreover, I'm getting duplicate rules -- one set of rules for 0.0.0.0/0 and another identical set for my VPC CIDR.

What can I do to help troubleshoot?

EDIT: This appears to have corrected itself after I removed the service and the NLB and then re-created the service. I still have duplicates though.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[selslack]

/remove-lifecycle stale

[nckturner]

/assign

[randomvariable]

/priority important-soon

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[selslack]

/remove-lifecycle stale

[TiagoJMartins]

I'm also being affected by this as the NLB needs to be recreated for the changes to take effect.

[larsrnielsen]

Facing the same issue. I have also tried to force a recreation of the NLB, but no luck on SG update

[M00nF1sh]

@larsrnielsen what's the k8s version used? the original issue should have already been addressed by https://github.com/kubernetes/kubernetes/pull/74692/files

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[nckturner]

/close

Please reopen this issue if its not fixed by kubernetes/kubernetes#74692

[k8s-ci-robot]

@nckturner: Closing this issue.

In response to this:

/close

Please reopen this issue if its not fixed by kubernetes/kubernetes#74692

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/test-infra repository.

[pasdam]

I'm still facing this issue in k8s 1.24

Server Version: version.Info{Major:"1", Minor:"24+", GitVersion:"v1.24.10-eks-48e63af", GitCommit:"9176fb99b52f8d5ff73d67fea27f3a638f679f8a", GitTreeState:"clean", BuildDate:"2023-01-24T19:17:48Z", GoVersion:"go1.19.5", Compiler:"gc", Platform:"linux/amd64"}

We have a loadbalancer service where we set loadBalancerSourceRanges, but the updates to this list don't propagate to the SG. Recreating the service is not an option for us, especially in production. Can we reopen this?

/reopen

[k8s-ci-robot]

@pasdam: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

I'm still facing this issue in k8s 1.24

Server Version: version.Info{Major:"1", Minor:"24+", GitVersion:"v1.24.10-eks-48e63af", GitCommit:"9176fb99b52f8d5ff73d67fea27f3a638f679f8a", GitTreeState:"clean", BuildDate:"2023-01-24T19:17:48Z", GoVersion:"go1.19.5", Compiler:"gc", Platform:"linux/amd64"}

We have a loadbalancer service where we set loadBalancerSourceRanges, but the updates to this list don't propagate to the SG. Recreating the service is not an option for us, especially in production. Can we reopen this?

/reopen

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/test-infra repository.