kubernetes/kops · error

error listing Keysets: %v

Error message

error listing Keysets: %v

What it means

Listing Keysets in the cluster's namespace via the Kops API failed during cluster deletion; the underlying error is an API-server request failure (connectivity, RBAC, or the API server being unavailable/tearing down).

Source

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

func (c *RESTClientset) DeleteCluster(ctx context.Context, cluster *kops.Cluster) error {
	configBase, err := registry.ConfigBase(c.VFSContext(), cluster)
	if err != nil {
		return err
	}

	err = vfsclientset.DeleteAllClusterState(ctx, configBase)
	if err != nil {
		return err
	}

	name := cluster.Name
	namespace := restNamespaceForClusterName(name)

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

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

View on GitHub (pinned to 4c8573c808)

Solutions

1. Verify the Kops API endpoint is reachable and healthy
2. Check the credentials/RBAC used by the clientset
3. Retry the delete operation once the API is responsive

When it happens

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