Install linkerd2 with helm and the pod can't start

[hantmac]

Hi I installed linkerd2 with helm (generate crt file myself using step), but the pod can't start.

The phenomenon is that it can run when it first started, but it will crashbackOff after a while.

[hantmac]

Some logs of controller:

WARN [     0.519595s] linkerd-identity.linkerd.svc.cluster.local:8080 linkerd2_proxy::proxy::reconnect connect error to ControlAddr { addr: Name(NameAddr { name: "linkerd-identity.linkerd.svc.cluster.local", port: 8080 }), identity: Some("linkerd-identity.linkerd.serviceaccount.identity.linkerd.cluster.local") }: request timed out
ERR! [     5.005343s] admin={bg=identity} linkerd2_proxy::app::identity Failed to certify identity: grpc-status: Unknown, grpc-message: "the request could not be dispatched in a timely fashion"
ERR! [     6.708854s] linkerd2_proxy::app::errors unexpected error: error trying to connect: Connection refused (os error 111) (address: 127.0.0.1:9995)
ERR! [    20.007933s] admin={bg=identity} linkerd2_proxy::app::identity Failed to certify identity: grpc-status: Unknown, grpc-message: "the request could not be dispatched in a timely fashion"
INFO [    29.708463s] linkerd2_proxy::signal received SIGTERM, starting shutdown

[Pothulapati]

@hantmac Can you tell us more information about the cluster configuration?, so that we can understand if there is anything different about the use-case.

[hantmac]

The k8s cluster version is 1.14.8, deploy on public cloud - ALiCloud, and the network can not access images on gcr.io . So I pull all the images used in linkerd and tag it , then push to our own docker harbor. I modify the image filed of values.yaml in helm chart .Finally, I install the linkerd :

helm install linkerd2   
--set-file global.identityTrustAnchorsPEM=ca.crt   
--set-file identity.issuer.tls.crtPEM=issuer.crt   
--set-file identity.issuer.tls.keyPEM=issuer.key  
 --set identity.issuer.crtExpiry=$exp   ./linkerd2

[ihcsim]

What command did you use to install Linkerd? All your control plane pods are missing the proxy sidecar containers. The READY field should at least say 0/2. A healthy installation will show 2/2:

NAME                                      READY   STATUS    RESTARTS   AGE
linkerd-controller-5fdff4bc9-9ln4z        2/2     Running   0          108m
linkerd-destination-775b667474-kgqn8      2/2     Running   0          108m
linkerd-grafana-59856fdb6c-ml2gq          2/2     Running   0          108m
linkerd-identity-858cc464f7-6pftn         2/2     Running   0          108m
linkerd-prometheus-86b8d4975d-bztdm       2/2     Running   0          108m
linkerd-proxy-injector-6567f54488-g5tvj   2/2     Running   0          108m
linkerd-sp-validator-68d9dd69d7-wxvgd     2/2     Running   0          108m
linkerd-tap-684bdf4db4-4lb56              2/2     Running   0          108m
linkerd-web-696457597b-6rxhw              2/2     Running   0          108m

[hantmac]

I install Linkerd with helm :

helm install linkerd2   
--set-file global.identityTrustAnchorsPEM=ca.crt   
--set-file identity.issuer.tls.crtPEM=issuer.crt   
--set-file identity.issuer.tls.keyPEM=issuer.key  
 --set identity.issuer.crtExpiry=$exp   ./linkerd2

Your sidecar means gcr.io/linkerd-io/proxy-init?

[ihcsim]

If you are using a private registry, you need both the gcr.io/linkerd-io/proxy-init and gcr.io/linkerd-io/proxy images.