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
LoadBalancer created by Cloud Controller Manager (CCM) is not getting cleaned up when the cluster is deleted. #1439
Comments
/cc @mkumatag |
I'm wondering what happens in the other platforms like AWS? Can we quickly check if it is getting cleaned up? if yes - how? |
In AWS case also, LB is not getting cleaned when we delete the hosted cluster. |
They have in-tree cloud-provider code handling this |
Created https://issues.redhat.com/browse/HOSTEDCP-486 for this since we use Jira for our own issue tracking |
Fixed in #1672 |
@alvaroaleman: Closing this issue. In response to this:
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. |
Observation:
service
namedrouter-default
of typeLoadBalancer
is created inopenshift-ingress
namespace on deployed cluster, CCM creates an external load balancer in the respective cloud for ingress purpose.service router-default
is deleted by CCM.service router-default
's status or it might have died during the clean up of management cluster's hosted cluster namespace - Need more exploration here).The text was updated successfully, but these errors were encountered: