linkerd2: error when try tap deploy

after install linkerd 2.10, and linkerd-viz I received erro on container of tap

[tap-95b9d8fcc-lgxms tap] time="2021-04-09T18:59:09Z" level=info msg="Tapping 5 pods for target: namespace:\"linkerd\"  type:\"deployment\"" 
[tap-95b9d8fcc-lgxms linkerd-proxy] [  1176.373105s]  WARN ThreadId(01) outbound:accept{client.addr=172.51.21.13:57292 target.addr=172.51.47.100:4190}: linkerd_app_core::errors: Failed to proxy request: request required the identity 'linkerd-identity.linkerd.serviceaccount.identity.linkerd.cluster.local' but no identity found 
[tap-95b9d8fcc-lgxms tap] time="2021-04-09T18:59:09Z" level=info msg="Establishing tap on 172.51.16.66:4190" 
[tap-95b9d8fcc-lgxms linkerd-proxy] [  1176.373479s]  WARN ThreadId(01) outbound:accept{client.addr=172.51.21.13:43774 target.addr=172.51.16.66:4190}: linkerd_app_core::errors: Failed to proxy request: request required the identity 'linkerd-proxy-injector.linkerd.serviceaccount.identity.linkerd.cluster.local' but no identity found 
[tap-95b9d8fcc-lgxms tap] time="2021-04-09T18:59:09Z" level=info msg="Establishing tap on 172.51.47.100:4190" 
[tap-95b9d8fcc-lgxms linkerd-proxy] [  1176.374342s]  WARN ThreadId(01) outbound:accept{client.addr=172.51.21.13:57106 target.addr=172.51.52.151:4190}: linkerd_app_core::errors: Failed to proxy request: request required the identity 'linkerd-controller.linkerd.serviceaccount.identity.linkerd.cluster.local' but no identity found 
[tap-95b9d8fcc-lgxms tap] time="2021-04-09T18:59:09Z" level=info msg="Establishing tap on 172.51.52.151:4190" 
[tap-95b9d8fcc-lgxms linkerd-proxy] [  1176.374410s]  WARN ThreadId(01) outbound:accept{client.addr=172.51.21.13:38408 target.addr=172.51.45.57:4190}: linkerd_app_core::errors: Failed to proxy request: request required the identity 'linkerd-destination.linkerd.serviceaccount.identity.linkerd.cluster.local' but no identity found 
[tap-95b9d8fcc-lgxms tap] time="2021-04-09T18:59:09Z" level=info msg="Establishing tap on 172.51.56.182:4190" 
[tap-95b9d8fcc-lgxms linkerd-proxy] [  1176.374464s]  WARN ThreadId(01) outbound:accept{client.addr=172.51.21.13:51712 target.addr=172.51.56.182:4190}: linkerd_app_core::errors: Failed to proxy request: request required the identity 'linkerd-sp-validator.linkerd.serviceaccount.identity.linkerd.cluster.local' but no identity found

I’ve restart deploy on linkerd and linkerd-viz namespaces but without sucess.

This is an EKS cluster v.1.18

linkerd check output

kubernetes-api
--------------
√ can initialize the client
√ can query the Kubernetes API

kubernetes-version
------------------
√ is running the minimum Kubernetes API version
√ is running the minimum kubectl version

linkerd-existence
-----------------
√ 'linkerd-config' config map exists
√ heartbeat ServiceAccount exist
√ control plane replica sets are ready
√ no unschedulable pods
√ controller pod is running

linkerd-config
--------------
√ control plane Namespace exists
√ control plane ClusterRoles exist
√ control plane ClusterRoleBindings exist
√ control plane ServiceAccounts exist
√ control plane CustomResourceDefinitions exist
√ control plane MutatingWebhookConfigurations exist
√ control plane ValidatingWebhookConfigurations exist
√ control plane PodSecurityPolicies exist

linkerd-identity
----------------
√ certificate config is valid
√ trust anchors are using supported crypto algorithm
√ trust anchors are within their validity period
√ trust anchors are valid for at least 60 days
√ issuer cert is using supported crypto algorithm
√ issuer cert is within its validity period
√ issuer cert is valid for at least 60 days
√ issuer cert is issued by the trust anchor

linkerd-webhooks-and-apisvc-tls
-------------------------------
√ proxy-injector webhook has valid cert
√ proxy-injector cert is valid for at least 60 days
√ sp-validator webhook has valid cert
√ sp-validator cert is valid for at least 60 days

linkerd-api
-----------
√ control plane pods are ready
√ can initialize the client
√ can query the control plane API

linkerd-version
---------------
√ can determine the latest version
√ cli is up-to-date

control-plane-version
---------------------
√ control plane is up-to-date
√ control plane and cli versions match

Status check results are √

Linkerd extensions checks
=========================

linkerd-viz
-----------
√ linkerd-viz Namespace exists
√ linkerd-viz ClusterRoles exist
√ linkerd-viz ClusterRoleBindings exist
√ tap API server has valid cert
√ tap API server cert is valid for at least 60 days
√ tap API service is running
√ linkerd-viz pods are injected
√ viz extension pods are running
√ prometheus is installed and configured correctly
√ can initialize the client
√ viz extension self-check

Status check results are √

Environment

• Kubernetes Version: 1.18.9
• Cluster Environment: EKS
• Host OS:

NAME                             STATUS   ROLES    AGE   VERSION              INTERNAL-IP      EXTERNAL-IP     OS-IMAGE         KERNEL-VERSION                  CONTAINER-RUNTIME
ip-172-51-117-154.ec2.internal   Ready    <none>   18h   v1.18.9-eks-d1db3c   172.51.117.154   X.X.X.X         Amazon Linux 2   4.14.225-169.362.amzn2.x86_64   docker://19.3.13
ip-172-51-12-18.ec2.internal     Ready    <none>   20h   v1.18.9-eks-d1db3c   172.51.12.18     X.X.X.X         Amazon Linux 2   4.14.225-169.362.amzn2.x86_64   docker://19.3.13
ip-172.51.58.13.ec2.internal     Ready    <none>   20h   v1.18.9-eks-d1db3c   172.51.58.13     X.X.X.X         Amazon Linux 2   4.14.225-169.362.amzn2.x86_64   docker://19.3.13

• Linkerd version: 2,10