kubernetes/kops · error

error deleting instance group %q: %v

Error message

error deleting instance group %q: %v

What it means

Deleting an individual InstanceGroup during teardown failed with a non-NotFound error; NotFound is tolerated as concurrent deletion, so this is a real API failure for that specific object after the list succeeded.

Source

Thrown at pkg/client/simple/api/clientset.go:176

			}
		}
	}

	{
		igs, err := c.KopsClient.InstanceGroups(namespace).List(ctx, metav1.ListOptions{})
		if err != nil {
			return fmt.Errorf("error listing instance groups: %v", err)
		}

		for i := range igs.Items {
			ig := &igs.Items[i]
			err = c.KopsClient.InstanceGroups(namespace).Delete(ctx, ig.Name, metav1.DeleteOptions{})
			if err != nil {
				if errors.IsNotFound(err) {
					// Unlikely...
					klog.Warningf("instance group was concurrently deleted")
				} else {
					return fmt.Errorf("error deleting instance group %q: %v", ig.Name, err)
				}
			}
		}
	}

	err = c.KopsClient.Clusters(namespace).Delete(ctx, name, metav1.DeleteOptions{})
	if err != nil {
		if errors.IsNotFound(err) {
			// Unlikely...
			klog.Warningf("cluster %q was concurrently deleted", name)
		} else {
			return fmt.Errorf("error deleting cluster%q: %v", name, err)
		}
	}

	return nil
}

View on GitHub (pinned to 4c8573c808)

Solutions

1. Check the wrapped API error for the actual cause
2. Retry kops delete cluster
3. Delete the named instance group manually if it remains

When it happens

Trigger: Thrown at pkg/client/simple/api/clientset.go:176 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of kubernetes/kops@4c8573c808 (2026-09-05). Data as JSON: /api/errors/b34a994ce1a85821. Report an issue: GitHub.