Closed
Description
What is the issue?
Linkerd-destination is crash looping on a bare-metal cluster, when I tried turning on debug logging there doesn't appear to be much information (attached below). No other pods in linkerd or other namespaces are crashing so it seems isolated with linkerd-destination
How can it be reproduced?
I created a bare metal cluster on Hetzner through Kubespray both terraform and ansible-playbook. And then get the error with both a helm install and using linkerd install | kubectl apply -f
my all.yaml: https://gist.github.com/Anthony-Bible/3e60e1d53d740d181569c82812e6d271
Logs, error output, etc
https://gist.github.com/Anthony-Bible/92d2fc4565081c0469d2f5302c3eb048
output of linkerd check -o short
Linkerd core checks
===================
linkerd-existence
-----------------
- pod/linkerd-destination-789cdbc9fd-bstdq container sp-validator is not ready
Status check results are √
\ pod/linkerd-destination-789cdbc9fd-bstdq container sp-validator is not ready
When the pod is ready, everything returns all green.
Environment
- Kubernetes: 1.21.11
- ubuntu 20.04
- linkerd: 2.11.1
Possible solution
No response
Additional context
No response
Would you like to work on fixing this bug?
No response