<p>I try to connect in the dashboard of kubernetes.</p>

<p>I have the latest version of kubernetes v1.12 with kubeadm , in a server.</p>

<p>I download from github the metrics-server and run: </p>

<blockquote>
  <p>Kubctl create -f deploy/1.8+</p>
</blockquote>

<p>but i get this error </p>

<blockquote>
  <p>kube-system   metrics-server-5cbbc84f8c-tjfxd   0/1    Pending 0 12m</p>
</blockquote>

<p>with out log to debug</p>

<blockquote>
  <p>error: the server doesn't have a resource type "logs"</p>
</blockquote>

<p>I don't want to install heapster because is DEPRECATED.</p>

<p><strong>UPDATE</strong></p>

<p>Hello, and thanks.</p>

<p>i run the taint command i get:</p>

<blockquote>
  <p>error: at least one taint update is required</p>
</blockquote>

<p>and the command </p>

<blockquote>
  <p>kubectl describe deployment metrics-server -n kube-system</p>
</blockquote>

<p>i get this output: </p>

<pre><code>Name:                   metrics-server
Namespace:              kube-system
CreationTimestamp:      Thu, 18 Oct 2018 14:34:42 +0000
Labels:                 k8s-app=metrics-server
Annotations:            deployment.kubernetes.io/revision: 1
 kubectl.kubernetes.io/last-applied-configuration:     {"apiVersion":"extensions/v1beta1","kind":"Deployment","metadata":    {"annotations":{},"labels":{"k8s-app":"metrics-server"},"name":"metrics-...
 Selector:               k8s-app=metrics-server
 Replicas:               1 desired | 1 updated | 1 total | 0 available | 1      unavailable
 StrategyType:           RollingUpdate
 MinReadySeconds:        0
 RollingUpdateStrategy:  1 max unavailable, 1 max surge
 Pod Template:
   Labels:           k8s-app=metrics-server
   Service Account:  metrics-server
   Containers:
    metrics-server:
Image:        k8s.gcr.io/metrics-server-amd64:v0.3.1
Port:         &lt;none&gt;
Host Port:    &lt;none&gt;
Environment:  &lt;none&gt;
Mounts:
  /tmp from tmp-dir (rw)
Volumes:
tmp-dir:
Type:    EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:  
 Conditions:
   Type           Status  Reason
   ----           ------  ------
   Available      True    MinimumReplicasAvailable
 OldReplicaSets:  &lt;none&gt;
 NewReplicaSet:   metrics-server-5cbbc84f8c (1/1 replicas created)
 Events:          &lt;none&gt;
</code></pre>

<p>Command:</p>

<blockquote>
  <p>kubectl get nodes</p>
</blockquote>

<p>The output for this is just the IP of the node, and nothing special.</p>

<p>Any ideas, or what to do to work the dashboard for kubernetes.</p>

pioupiou
<p>I suppose you are trying setup metrics-server on your master node.</p>

<p>If you issue  <code>kubectl describe deployment metrics-server -n kube-system</code> I believe you will see something like this:</p>

<blockquote>
  <p>Name:                   metrics-server Namespace:<br>
  kube-system CreationTimestamp:      Thu, 18 Oct 2018 15:57:34 +0000
  Labels:                 k8s-app=metrics-server Annotations:<br>
  deployment.kubernetes.io/revision: 1 Selector:<br>
  k8s-app=metrics-server Replicas:               1 desired | 1 updated |
  1 total | 0 available | 1 unavailable</p>
</blockquote>

<p>But if you will describe your node you will see taint that prevent you from scheduling new pods on master node:</p>

<pre><code>kubectl get nodes

NAME            STATUS   ROLES    AGE   VERSION
kube-master-1   Ready    master   17m   v1.12.1

kubectl describe node kube-master-1

Name:               kube-master-1
...
Taints:             node-role.kubernetes.io/master:NoSchedule
</code></pre>

<p>You have to remove this taint:</p>

<pre><code>kubectl taint node kube-master-1 node-role.kubernetes.io/master:NoSchedule-
node/kube-master-1 untainted
</code></pre>

<p>Result:</p>

<pre><code> kubectl get pods --all-namespaces

NAMESPACE     NAME                                    READY   STATUS    RESTARTS   AGE
kube-system   calico-node-xvc77                       2/2     Running   0          20m
kube-system   coredns-576cbf47c7-rj4wh                1/1     Running   0          21m
kube-system   coredns-576cbf47c7-vsjsf                1/1     Running   0          21m
kube-system   etcd-kube-master-1                      1/1     Running   0          20m
kube-system   kube-apiserver-kube-master-1            1/1     Running   0          20m
kube-system   kube-controller-manager-kube-master-1   1/1     Running   0          20m
kube-system   kube-proxy-xp5zh                        1/1     Running   0          21m
kube-system   kube-scheduler-kube-master-1            1/1     Running   0          20m
kube-system   metrics-server-5cbbc84f8c-l2t76         1/1     Running   0          18m
</code></pre>

<p>But this is not the best approach. Good approach is to join worker and set up metrics-server there. There won't be any issues and there is no need to touch taint on master node.</p>

<p>Hope it will help you.</p>
