Linkerd fails to install, no running pods for linkderd-distination

Linkerd General Discussion
1

Hi,

I have a few clusters with Linkerd on them, but I was just building a new cluster and trying to install linkerd, but it keeps failing with bad request and the pods fail to launch.

The Compatibility page might be the answer as I’m running 1.32.5+k3s1 and that page notes that the maximum version is 1.31. Though I want to ask.

Compatibility Link: Supported Kubernetes Versions | Linkerd

Hypervisor used: Harvester & Proxmox
Kubernetes Nodes Used: Rocky Linux 10 and 9.6
Kubernetes Version: v1.32.5+k3s1

Linkerd Check Error Screenshot.

linkerd_fail
linkerd_fail581×329 5.89 KB

kubectl logs:

 $ k get all -n linkerd
NAME                                          READY   STATUS                  RESTARTS        AGE
pod/linkerd-destination-6565bbbdd6-9fmrk      0/4     Init:Error              7 (5m11s ago)   11m
pod/linkerd-identity-6b7cd4467f-56jgj         0/2     Init:Error              7 (5m17s ago)   11m
pod/linkerd-proxy-injector-5cbd54b7dd-z78dp   0/2     Init:CrashLoopBackOff   7 (18s ago)     11m


$ k logs linkerd-destination-6565bbbdd6-9fmrk -n linkerd

Defaulted container "linkerd-proxy" out of: linkerd-proxy, destination, sp-validator, policy, linkerd-init (init)
Error from server (BadRequest): container "linkerd-proxy" in pod "linkerd-destination-6565bbbdd6-9fmrk" is waiting to start: PodInitializing


$ k logs linkerd-identity-6b7cd4467f-56jgj -n linkerd

Defaulted container "identity" out of: identity, linkerd-proxy, linkerd-init (init)
Error from server (BadRequest): container "identity" in pod "linkerd-identity-6b7cd4467f-56jgj" is waiting to start: PodInitializing


$ k logs linkerd-proxy-injector-5cbd54b7dd-z78dp -n linkerd

Defaulted container "linkerd-proxy" out of: linkerd-proxy, proxy-injector, linkerd-init (init)
Error from server (BadRequest): container "linkerd-proxy" in pod "linkerd-proxy-injector-5cbd54b7dd-z78dp" is waiting to start: PodInitializing

Thanks for any help provided.
Dave

2

Hi Dave,

The Init:Error status indicates that the init container has failed. You can get more information by running:

kubectl logs -n linkerd linkerd-destination-6565bbbdd6-9fmrk -c linkerd-init

Linkerd-init is responsible for rewriting your iptables rules so that all inbound and outbound traffic is routed through the proxy.

Also, what version of Linkerd are you using?

Source Code: linkerd2-proxy-init/pkg/iptables/iptables.go at main · linkerd/linkerd2-proxy-init · GitHub

3

Thank you, that was the logs info I needed.

For posterity purposes, my issue was I needed to load two modules on the cluster nodes to enable the functionality required by the ipables commands.

  1. modprobe xt_REDIRECT
  2. modprobe xt_owner

Dave