-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kops does not delete NLB load balancers #4672
Comments
I think this is an open issue upstream. @micahhausler any recommendations? |
I think this is likely a kops issue (assuming the NLB is tagged). When kops deletes a cluster, it deletes the resources which were created by that cluster also (e.g. EBS volumes). I presume that's what you mean @jpds - you created an NLB using the magic annotation on a service of |
Hi - this also occurs using kops 1.9.0 and kubernetes 1.9.7. kops delete cluster --name=${NAME} --yes eventually times out trying to delete the VPC because there is still nlb(s) that havent been cleaned up. And yes @justinsb in our case the NLBs were created using the magic annotation on a service of Type: LoadBalancer. |
It appears that NLBs and ALBs are only supported in aws sdk package |
FYI, I am working on this feature. I am plugging in additional method to get ELBV2 resources and delete them just like how we do it for regular Load Balancers. |
Thanks @nareshku ! |
@justinsb I am kind of stuck in here and hoping you can help me with this. I am able to get the functionality of discovering and deleting the resources working, but only with something like below: https://github.com/nareshku/kops/blob/support-albs-nlbs/pkg/resources/aws/aws.go#L1569-L1570
instead of
I am getting the below null pointer exception.
|
I did a print on the cloud interface and seems like
|
never mind, I have found where to initialize session for ELBV2. |
kops
version are you running? The commandkops version
, will displaythis information.
1.9.0-alpha1
kubectl version
will print theversion if a cluster is running or provide the Kubernetes version specified as
a
kops
flag.1.9.3
AWS.
kops delete cluster --name=${NAME} --yes
Kubernetes nodes were torn down by the NLB provisioned through a LoadBalancer service stayed which blocked the deletion of the internet-gateway for the VPC.
kops delete cluster
deletes the NLB.The text was updated successfully, but these errors were encountered: