kubernetes/kops · error

error listing instance groups: %v

Error message

error listing instance groups: %v

What it means

Listing InstanceGroups in the cluster's namespace failed during cluster deletion; an API-level failure (connectivity, auth, or the API server disappearing mid-delete) that halts teardown before the IG objects are removed.

Source

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

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

	{
		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 {

View on GitHub (pinned to 4c8573c808)

Solutions

1. Verify the Kops API endpoint is reachable and healthy
2. Check client credentials and RBAC for listing instance groups
3. Retry the delete once the API responds

When it happens

Trigger: Thrown at pkg/client/simple/api/clientset.go:165 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/4b803042d1dff4a8. Report an issue: GitHub.