Getting Started: Unable to run emojivoto demo app?

[sheeeng]

Had issues at this Step 4: Install the demo app step.

➜  ~ $ linkerd check
kubernetes-api
--------------
√ can initialize the client
√ can query the Kubernetes API

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

linkerd-existence
-----------------
√ 'linkerd-config' config map exists
√ heartbeat ServiceAccount exist
√ control plane replica sets are ready
√ no unschedulable pods
√ control plane pods are ready
√ cluster networks contains all node podCIDRs
√ cluster networks contains all pods
√ cluster networks contains all services

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
√ proxy-init container runs as root user if docker container runtime is used

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
√ policy-validator webhook has valid cert
√ policy-validator cert is valid for at least 60 days

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

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

linkerd-control-plane-proxy
---------------------------
√ control plane proxies are healthy
√ control plane proxies are up-to-date
√ control plane proxies and cli versions match

Status check results are √
➜  ~ $

➜  ~ $ curl --proto '=https' --tlsv1.2 -sSfL https://run.linkerd.io/emojivoto.yml \
  | kubectl apply -f -
namespace/emojivoto created
serviceaccount/emoji created
serviceaccount/voting created
serviceaccount/web created
service/emoji-svc created
service/voting-svc created
service/web-svc created
deployment.apps/emoji created
deployment.apps/vote-bot created
deployment.apps/voting created
deployment.apps/web created
➜  ~ $

➜  ~ $ kubectl -n emojivoto port-forward svc/web-svc 8080:80
error: unable to forward port because pod is not running. Current status=Pending
➜  ~ $ kubectl -n emojivoto get pods
NAME                        READY   STATUS    RESTARTS   AGE
emoji-5f844f4cb5-vpztk      0/1     Pending   0          52s
vote-bot-5c64bd6898-8j2z8   1/1     Running   0          52s
voting-7b77644858-v2ddp     0/1     Pending   0          52s
web-58fb4f6fb6-d7747        0/1     Pending   0          52s
➜  ~ $ kubectl -n emojivoto logs emoji-5f844f4cb5-vpztk
➜  ~ $ kubectl -n emojivoto logs voting-7b77644858-v2ddp
➜  ~ $ kubectl -n emojivoto logs web-58fb4f6fb6-d7747
➜  ~ $

How to further troubleshoot this issue?

[alpeb]

Those workloads haven't been injected by linkerd yet, so it must be an issue with your cluster unrelated to linkerd. I would start by issuing kubectl describe on those pods to get more info.