kubernetes/kops · error

error reading kubeconfig: %v

Error message

error reading kubeconfig: %v

What it means

Reading the existing kubeconfig via GetStartingConfig failed while writing a new one; a parse or I/O error on the current kubeconfig file prevents merging the new context into it.

Source

Thrown at pkg/kubeconfig/kubecfg_builder.go:85

	delete(config.Contexts, b.Context)

	if config.CurrentContext == b.Context {
		config.CurrentContext = ""
	}

	if err := clientcmd.ModifyConfig(configAccess, *config, false); err != nil {
		return fmt.Errorf("error writing kubeconfig: %v", err)
	}

	fmt.Printf("Deleted kubectl config for %s\n", b.Context)
	return nil
}

// Write out a new kubeconfig
func (b *KubeconfigBuilder) WriteKubecfg(configAccess clientcmd.ConfigAccess) error {
	config, err := configAccess.GetStartingConfig()
	if err != nil {
		return fmt.Errorf("error reading kubeconfig: %v", err)
	}

	if config == nil {
		config = &clientcmdapi.Config{}
	}

	{
		cluster := config.Clusters[b.Context]
		if cluster == nil {
			cluster = clientcmdapi.NewCluster()
		}
		cluster.Server = b.Server
		cluster.TLSServerName = b.TLSServerName
		cluster.CertificateAuthorityData = b.CACerts

		if config.Clusters == nil {
			config.Clusters = make(map[string]*clientcmdapi.Cluster)
		}

View on GitHub (pinned to 4c8573c808)

Solutions

1. Fix or regenerate the existing kubeconfig
2. Check file permissions
3. Remove the corrupt kubeconfig so it can be recreated

When it happens

Trigger: Thrown at pkg/kubeconfig/kubecfg_builder.go:85 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/ef32daf340100d0f. Report an issue: GitHub.