Help with GKE Node Pool stuck in STOPPING status

Hi all,

We recently applied a terraform plan to destroy some unneeded CI/CD runners in GKE; the cluster was removed, but the node pool is still hanging around (it’s visible as a resource in Asset Inventory), and showing as status STOPPING.

Since the cluster is gone, we can’t access the node pool via the UI or gcloud CLI as everything needs to go through the parent cluster first.

Does anyone have suggestions on how we can view & diagnose why the node pool isn’t being removed? We’re at about 6 days now, and while there’s no heavily adverse effects, it does mean that our tf state shows as consistently out of date, and that apply jobs are being marked as fails.

Appreciate any suggestions you all might have.

1 Like