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
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:
the fwd rules. gcloud compute forwarding-rules delete xxx
the backend-services. get from gcloud compute backend-services list.
The text was updated successfully, but these errors were encountered:
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
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.
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:
gcloud compute forwarding-rules delete xxx
gcloud compute backend-services list
.The text was updated successfully, but these errors were encountered: