Linkerd Destination Pod Unhealthy Warnings

[jaswanth9522]

What is the issue?

Linkerd Destination pod unhealthy warnings in events

How can it be reproduced?

Install stable-2.14.5 helm chart

Logs, error output, etc

Warning Unhealthy pod/linkerd-destination-randomhash Liveness probe failed: Get "http://myIP:9996/ping": dial tcp myIP:9996: i/o timeout (Client.Timeout exceeded while awaiting headers)

10m Warning Unhealthy pod/linkerd-destination-randomhash Readiness probe failed: Get "http://myIP:9990/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

output of linkerd check -o short

control plane CustomResourceDefinitions exist
CRD servers.policy.linkerd.io is missing version v1beta2, missing grpcroutes.gateway.networking.k8s.io, missing externalworkloads.workload.linkerd.io
see https://linkerd.io/2/checks/#l5d-existence-crd for hints

                          linkerd

linkerd-smi

‼ Linkerd extension command linkerd-smi exists
exec: "linkerd-smi": executable file not found in %PATH%
see https://linkerd.io/2/checks/#extensions for hints

Status check results are ×

Environment

Kubernetes version: v1.28.10+rke2r1
Cluster env: On premise
Host OS: Oracle Linux Server 8.10
Linkerd version: stable-2.14.5

Possible solution

Is there any possibility to add the readiness and liveness probes from values file instead of getting them from templates and
so that we can increase the default values like timeout seconds etc.

Additional context

No response

Would you like to work on fixing this bug?

None

[mateiidavid]

@jaswanth9522 hi, if this is about setting timeouts in the values file for probes, Linkerd already supports that for a variety of components. Have a look for example at

linkerd2/charts/linkerd-control-plane/values.yaml

Lines 232 to 239 in 332c4ef

	# -- ReadinessProbe timeout and delay configuration
	readinessProbe:
	initialDelaySeconds: 2
	timeoutSeconds: 1
	startupProbe:
	initialDelaySeconds: 0
	periodSeconds: 1
	failureThreshold: 120

.

These will be present in recent edge versions, so I would suggest upgrading to make use of it. You can have a look at the original issue (#11453) for more information.

Let me know if this makes sense. :)

[kristjankullerkann-wearemp]

Duplicate of #12895

cc: @alpeb