kubernetes/kops · error

failed to initialize the node controller, error: %v

Error message

failed to initialize the node controller, error: %v

What it means

initializeWatchers in dns-controller wraps any failure from watchers.NewNodeController. The node controller (which translates Kubernetes node changes into DNS records) could not be constructed, so DNS-controller startup aborts with this message and the underlying cause appended.

Source

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

	}

	// @step: initialize the watchers
	if err := initializeWatchers(client, dnsController, watchNamespace, watchIngress, internalRecordTypes); err != nil {
		klog.Errorf("%s", err)
		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)
		}

View on GitHub (pinned to 4c8573c808)

Solutions

1. Inspect the wrapped inner error (%v) to find the actual constructor failure.
2. Verify the kubernetes clientset was built successfully from a valid kubeconfig/in-cluster config.
3. Check the --internal-record-types flag values are valid dns.RecordType entries.

Example fix

// before
client, err := buildClient() // err ignored
initializeWatchers(client, dnsctl, ns, true, types)
// after
if err != nil { klog.Fatalf("building client: %v", err) }

if client == nil {
	return errors.New("kubernetes client must be initialized before creating watchers")
}
if dnsctl == nil {
	return errors.New("dns controller must be initialized before creating watchers")
}

func validWatchersInputs(client kubernetes.Interface, dnsctl *dns.DNSController) bool {
	return client != nil && dnsctl != nil
}

if err := initializeWatchers(client, dnsctl, ns, watchIngress, types); err != nil {
	klog.Fatalf("initializeWatchers: %v", err) // inspect wrapped cause
}

When it happens

Trigger: Calling NewNodeController with a nil/invalid kubernetes client, a nil DNS controller, or an invalid internalRecordTypes list causes the constructor to return an error which is wrapped here.

Common situations: Kubernetes client failed to build (bad kubeconfig) so a nil/degraded client is passed; misconfigured record-type flags producing invalid dns.RecordType values.

Related errors

• failed to initialize the pod 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/d077416b486821c0. Report an issue: GitHub.