Hello,
We are using ingress as Kong ingress controller and service mesh as Linkerd. We noticed suddenly the kong ingress controller is failing to start, upon checking we can follow errors in the pod log,
[ 0.001958s] INFO ThreadId(01) linkerd2_proxy: Identity verified via linkerd-identity-headless.linkerd.svc.cluster.local:80 (linkerd-identity.linkerd.serviceaccount.identity.linkerd.cluster.local)
[ 0.001960s] INFO ThreadId(01) linkerd2_proxy: Destinations resolved via linkerd-dst-headless.linkerd.svc.cluster.local:8086 (linkerd-destination.linkerd.serviceaccount.identity.linkerd.cluster.local)
[ 0.040911s] INFO ThreadId(02) daemon:identity: linkerd_app: Certified identity id=ingress-controller-kong.kong.serviceaccount.identity.linkerd.cluster.local
[ 1.494493s] INFO ThreadId(01) outbound: linkerd_app_core::serve: Connection closed error=connect timed out after 1s client.addr=172.16.9.13:51610
[ 9.374208s] INFO ThreadId(01) inbound: linkerd_app_core::serve: Connection closed error=http2 error: connection error detected: unspecific protocol error detected error.sources=[connection error detected: unspecific protocol error detected] client.addr=172.16.2.37:59440
[ 9.465979s] INFO ThreadId(01) inbound: linkerd_app_core::serve: Connection closed error=http2 error: connection error detected: unspecific protocol error detected error.sources=[connection error detected: unspecific protocol error detected] client.addr=172.16.2.37:59454
We are not seeing any issue with Linkerd pods. Any help will be much appreciated.
Thanks