kubernetes/kops · error

error building kube-apiserver manifest: %v

Error message

error building kube-apiserver manifest: %v

What it means

Wraps a failure of buildPod in the kube-apiserver builder: the static pod manifest for kube-apiserver could not be assembled (flags, volumes, or hooks construction failed) before it is marshaled and written to /etc/kubernetes/manifests.

Source

Thrown at nodeup/pkg/model/kube_apiserver.go:241

		kubeAPIServer.ProxyClientKeyFile = new(filepath.Join(pathSrvKAPI, "apiserver-aggregator.key"))
	}

	if err := b.writeServerCertificate(c, &kubeAPIServer); err != nil {
		return err
	}

	if err := b.writeKubeletAPICertificate(c, &kubeAPIServer); err != nil {
		return err
	}

	if err := b.writeStaticCredentials(c, &kubeAPIServer); err != nil {
		return err
	}

	{
		pod, err := b.buildPod(ctx, &kubeAPIServer)
		if err != nil {
			return fmt.Errorf("error building kube-apiserver manifest: %v", err)
		}

		manifest, err := k8scodecs.ToVersionedYaml(pod)
		if err != nil {
			return fmt.Errorf("error marshaling manifest to yaml: %v", err)
		}

		c.AddTask(&nodetasks.File{
			Path:     "/etc/kubernetes/manifests/kube-apiserver.manifest",
			Contents: fi.NewBytesResource(manifest),
			Type:     nodetasks.FileType_File,
		})
	}

	// If we're using kube-apiserver-healthcheck, we need to set up the client cert etc
	if b.findHealthcheckManifest() != nil {
		if err := b.addHealthcheckSidecarTasks(c); err != nil {
			return err

View on GitHub (pinned to 4c8573c808)

Solutions

1. Check nodeup logs for the underlying build error
2. Validate kubeAPIServer flags in the cluster spec
3. Re-run nodeup after fixing the spec

When it happens

Trigger: Thrown at nodeup/pkg/model/kube_apiserver.go:241 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/602fd21b2b03331a. Report an issue: GitHub.