kubernetes/kops · error

failed to initialize the pod controller, error: %v

Error message

failed to initialize the pod controller, error: %v

What it means

initializeWatchers wraps failures from watchers.NewPodController. The pod controller could not be created, so dns-controller stops starting watchers and returns this wrapped error, which main aborts on.

Source

Thrown at dns-controller/cmd/dns-controller/main.go:163

		os.Exit(1)
	}

	// start and wait on the dns controller
	dnsController.Run()
}

// initializeWatchers is responsible for creating the watchers
func initializeWatchers(client kubernetes.Interface, dnsctl *dns.DNSController, namespace string, watchIngress bool, internalRecordTypes []dns.RecordType) error {
	klog.V(1).Infof("initializing the watch controllers, namespace: %q", namespace)

	nodeController, err := watchers.NewNodeController(client, dnsctl, internalRecordTypes)
	if err != nil {
		return fmt.Errorf("failed to initialize the node controller, error: %v", err)
	}

	podController, err := watchers.NewPodController(client, dnsctl, namespace)
	if err != nil {
		return fmt.Errorf("failed to initialize the pod controller, error: %v", err)
	}

	serviceController, err := watchers.NewServiceController(client, dnsctl, namespace)
	if err != nil {
		return fmt.Errorf("failed to initialize the service controller, error: %v", err)
	}

	var ingressController *watchers.IngressController
	if watchIngress {
		ingressController, err = watchers.NewIngressController(client, dnsctl, namespace)
		if err != nil {
			return fmt.Errorf("failed to initialize the ingress controller, error: %v", err)
		}
	} else {
		klog.Infof("Ingress controller disabled")
	}

	go nodeController.Run()

View on GitHub (pinned to 4c8573c808)

Solutions

1. Read the wrapped inner error for the real cause.
2. Validate the --namespace flag value (must be a valid DNS-1123 label or empty for all namespaces).
3. Ensure the Kubernetes client is functional (kubectl auth cani / connection check with same kubeconfig).

Example fix

// before
initializeWatchers(client, dnsctl, "", true, types) // invalid namespace
// after
initializeWatchers(client, dnsctl, "kube-system", true, types)

if namespace != "" {
	if errs := validation.IsDNS1123Label(namespace); len(errs) > 0 {
		return fmt.Errorf("invalid namespace %q: %v", namespace, errs)
	}
}

func isValidNamespace(ns string) bool {
	return ns == "" || validation.IsDNS1123Label(ns) == nil
}

if err := initializeWatchers(client, dnsctl, ns, true, types); err != nil {
	klog.Fatalf("watchers init failed: %v", err)
}

When it happens

Trigger: NewPodController receives a nil/invalid kubernetes.Interface, a nil DNSController, or an empty/invalid namespace and returns an error.

Common situations: The --namespace flag is set to an empty or invalid value; client construction partially failed; upstream API machinery returned an error during informer setup.

Related errors

• failed to initialize the node controller, error: %v
• failed to initialize the service controller, error: %v
• failed to initialize the ingress controller, error: %v
• error initializing DNS cache: %v
• error listing nodes: %v

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