You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Created a service with k8s v1.9.0 and NLB annotation, then deleted it. The security group rules created for the NLB didn't get deleted.
What you expected to happen:
The Security group rules for NLB should have been removed. The kubernetes-controller-manager emitted this log:
W1222 20:42:15.153263 5 aws.go:2818] Error revoking security group ingress: "InvalidParameterValue: missing mandatory parameter: exactly one of remote-security-group, remote-ip-range, remote-ipv6-range, or prefix-list-id must be present\n\tstatus code: 400, request id: 65413c4f-b534-4b35-b70c-66b2169be1d4"
How to reproduce it (as minimally and precisely as possible):
With a K8s 1.9 cluster and grant k8s 1.9 additional permissions (Until kubernetes/kops#4095 lands in a kops release)
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.
Fix AWS NLB delete error
**What this PR does / why we need it**:
Fixes an error when deleting an NLB in AWS
**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:
Fixes#57568
**Special notes for your reviewer**:
**Release note**:
```release-note
Fixes an error when deleting an NLB in AWS - Fixes#57568
```
@justinsb How do I get this into the `release-1.9` branch?
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
/sig aws
What happened:
Created a service with k8s v1.9.0 and NLB annotation, then deleted it. The security group rules created for the NLB didn't get deleted.
What you expected to happen:
The Security group rules for NLB should have been removed. The kubernetes-controller-manager emitted this log:
How to reproduce it (as minimally and precisely as possible):
With a K8s 1.9 cluster and grant k8s 1.9 additional permissions (Until kubernetes/kops#4095 lands in a kops release)
Create a service:
Anything else we need to know?:
Environment:
kubectl version
):v1.9.0
uname -a
):Linux ip-172-20-120-154 4.4.102-k8s #1 SMP Sun Nov 26 23:32:43 UTC 2017 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: