Transparent proxy feature: linkerd pod stays in init state

Help Kubernetes
#1

Following the doc, https://linkerd.io/features/transparent-proxying/ I enabled transparent proxing feature on linkerd in both ways i.e; linkerd-inject & manual process, but the pod stays in init state

l5d-rj3x6                          0/1       Init:1/2   2          3m

kubectl logs -f l5d-rj3x6 -c l5d

Error from server (BadRequest): container "l5d" in pod "l5d-rj3x6" is waiting to start: PodInitializing

kubectl describe pod l5d-rj3x6 

  1m            1m              3       kubelet, ip-xx-x-xxx-x.us-west-2.compute.internal       spec.initContainers{init-linkerd}    Warning          BackOff                 Back-off restarting failed container
  1m            52s             3       kubelet, ip-xx-x-xxx-x.us-west-2.compute.internal       spec.initContainers{init-linkerd}    Normal           Pulled                  Container image "linkerd/istio-init:v1" already present on machine
  1m            52s             3       kubelet, ip-xx-x-xxx-x.us-west-2.compute.internal       spec.initContainers{init-linkerd}    Normal           Created                 Created container
  1m            52s             3       kubelet, ip-xx-x-xxx-x.us-west-2.compute.internal       spec.initContainers{init-linkerd}    Normal           Started                 Started container
  1m            52s             5       kubelet, ip-xx-x-xxx-x.us-west-2.compute.internal                                            Warning          FailedSync              Error syncing pod
  51s           51s             1       kubelet, ip-xx-x-xxx-x.us-west-2.compute.internal       spec.initContainers{kubectl}         Normal           Pulled                  Container image "buoyantio/kubectl:v1.4.0" already present on machine
  51s           51s             1       kubelet, ip-xx-x-xxx-x.us-west-2.compute.internal       spec.initContainers{kubectl}         Normal           Created                 Created container
  51s           51s             1       kubelet, ip-xx-x-xxx-x.us-west-2.compute.internal       spec.initContainers{kubectl}         Normal           Started                 Started container

Setup

  • linkerd v1.3.1
  • k8s 1.7
  • cloud provider AWS

configmap.yml (649 Bytes)
linkerd.yml (4.2 KB)

#2

Hi @zshaik,

How long does the pod stay in the init state? It’s normal for this to take a few minutes.

#3

@eliza almost forever, been 17h now its still in init state

l5d-wndn2 0/1 Init:1/2 4 17h

#4

Okay, that definitely seems like a problem!

Earlier you said

Does that mean you ran linkerd-inject and added the initContainer to your configs manually for the same attempt to deploy Linkerd, or you made separate attempts, once with linkerd-inject and once by adding the configuration manually?

1 Like
#5

@eliza separate attempts

  • using linkerd-inject
  • using initContainer config