Fresh install with emojivoto - Dashboard success rate

[Monkman08]

Bug Report

What is the issue?

On a fresh cluster, with fresh linkerd and emojovoto installed. the success rate in the dashboard for emojivoto is showing around 80% success (unhealthy) even after a number of hours and restarts. According to the linkerd dashboard all the pods in the linkerd namespace are showing 100% success rate and are green.

IMAGE: https://imgur.com/a/E5VrtIF

How can it be reproduced?

Logs, error output, etc

There are no linkerd-proxy errors for any of the emojivoto pods (with the standard log level)

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
√ can initialize the client
√ can query the control plane API

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-api
-----------
√ control plane pods are ready
√ control plane self-check
√ [kubernetes] control plane can talk to Kubernetes
√ [prometheus] control plane can talk to Prometheus
√ tap api service is running

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

linkerd-addons
--------------
√ 'linkerd-config-addons' config map exists

linkerd-grafana
---------------
√ grafana add-on service account exists
√ grafana add-on config map exists
√ grafana pod is running

Status check results are √```

### Environment

- Kubernetes Version: 1.16
- Cluster Environment: EKS
- Host OS: AWS EKS AMI
- Linkerd version: stable-2.8.1

### Possible solution

### Additional context
EKS version is not the latest because i mirrored a production environment to compare.

[grampelberg]

Yup, there's a bug in emojivoto on purpose. We use that to show off how you can debug issues with your service! You'll notice there's a link at the bottom of getting started to debugging your service. That'll walk you through finding the bug =)