Node-pool deletion doesn't fully delete with Talos

[NerdyShawn]

Had an existing Talos cluster where I wanted to try to add a net new named node-pool to a cluster and then delete it

civo k8s node-pool create test02 --name somename -s g4s.kube.xsmall
The pool (somename) was added to the cluster (test02)

That scaled up and was ok, I shortly after then attempted a cli removal

civo k8s node-pool delete test02 somename
Warning: Are you sure you want to delete the somename node pool (y/N) ? y
The node pool (somename) has been deleted from the cluster (test02)

The ui says 4 nodes, but when you click on it says 1 node

From the cluster's perspective I see the nodes still there but with scheduling disabled

k get nodes
NAME                                 STATUS                     ROLES    AGE     VERSION
test02-889a-a0ac4c-pool-9022-6mh3s   Ready,SchedulingDisabled   <none>   5h18m   v1.25.5
test02-889a-a0ac4c-pool-9022-bwsq2   Ready,SchedulingDisabled   <none>   5h17m   v1.25.5
test02-889a-a0ac4c-pool-9022-q9syi   Ready,SchedulingDisabled   <none>   5h18m   v1.25.5
test02-889a-a0ac4c-pool-c4a5-is9op   Ready                      <none>   27h     v1.25.5

About 4 hours later I attempted the delete operation again via CLI without change.
The node-pool doesn't exist in the specific cluster ui, only the main "kubernetes" menu from the web ui in civo account.

I then attempted the same process with k3s type cluster and the named node-pool delete was successful in node-removal so the issue seems specific to Talos type clusters, this was tested in NYC1.

[RealHarshThakur]

Hey @NerdyShawn , we're looking into this. Thanks for reporting