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

Failed to delete Internal LB resources when k8s service was deleted on GKE #436

Open
yandongxiao opened this issue Feb 1, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@yandongxiao
Copy link
Collaborator

Describe the bug

This only happens on internal LB (not on external LB). When we uninstall SR cluster, the LB related GCP resource is not cleaned up, making the next round of SR helm install failing. It complains the LB IP I pre-alloc and put in helm yaml file - still IN USE.

I had to delete the related resources to enable SR cluster reinstall. Including:

  1. the fwd rules. gcloud compute forwarding-rules delete xxx
  2. the backend-services. get from gcloud compute backend-services list.
@yandongxiao yandongxiao added the bug Something isn't working label Feb 1, 2024
@yandongxiao yandongxiao changed the title Failed to delete Internal LB resources when k8s service was deleted Failed to delete Internal LB resources when k8s service was deleted on GKE Feb 1, 2024
@yandongxiao
Copy link
Collaborator Author

StarRocks Operator now does not handle GCP related resources. It just delete the resource it created.
StarRocks Operator does not do anything adaptation on public provider.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant