Skip to content
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

Closed
dharaneeshvrd opened this issue Jun 6, 2022 · 7 comments

Comments

@dharaneeshvrd
Copy link
Member

Observation:

  • Currently when we create and delete the hypershift cluster, below is the observation,
  • Hypershift cluster is created with hypershift cli. Control plane components are set up and running,service named router-default of type LoadBalancer is created in openshift-ingress namespace on deployed cluster, CCM creates an external load balancer in the respective cloud for ingress purpose.
  • This LoadBalancer will get deleted only when service router-default is deleted by CCM.
  • When we delete the cluster by deleting the hosted cluster, everything getting cleaned up on the deployed cluster and control plane components deployed in management cluster in hosted cluster namespace is getting deleted.
  • But external LoadBalancer is not getting cleaned with the above process. (possible reason could be API server might become unreachable to CCM to check the 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).
@dharaneeshvrd
Copy link
Member Author

/cc @mkumatag

@mkumatag
Copy link
Member

mkumatag commented Jun 6, 2022

I'm wondering what happens in the other platforms like AWS? Can we quickly check if it is getting cleaned up? if yes - how?

@dharaneeshvrd
Copy link
Member Author

In AWS case also, LB is not getting cleaned when we delete the hosted cluster.
Could not figure out which component is responsible for create and delete LB in AWS case, since CCM is not involved.

@mkumatag
Copy link
Member

mkumatag commented Jun 6, 2022

In AWS case also, LB is not getting cleaned when we delete the hosted cluster.
Could not figure out which component is responsible for create and delete LB in AWS case, since CCM is not involved.

They have in-tree cloud-provider code handling this

@alvaroaleman
Copy link
Contributor

Created https://issues.redhat.com/browse/HOSTEDCP-486 for this since we use Jira for our own issue tracking

@alvaroaleman
Copy link
Contributor

Fixed in #1672
/close

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 17, 2022

@alvaroaleman: Closing this issue.

In response to this:

Fixed in #1672
/close

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.

@openshift-ci openshift-ci bot closed this as completed Aug 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants