Heapster doesn't work

[vide]

Hello, first of all thanks for you HOWTO, it made possible to easily create an HA k8s cluster in about 1-hour! I've used the 1.7 version, just replacing the 1.7.0 components for the latest minor version (1.7.8), everything works fine a part from Heapster. There's no way to get the Dashboard to display anything, and I can't see any useful message in logs. What could it be?

[mottycruz]

can you edit heapster in "Deployments" and change heapster version? I am running

name    :    heapster

image    :    gcr.io/google_containers/heapster-amd64:v1.3.0

Thanks, Motty

On 10/18/2017 8:08 AM, Davide Ferrari wrote:

Hello, first of all thanks for you HOWTO, it made possible to easily create an HA k8s cluster in about 1-hour! I've used the 1.7 version, just replacing the 1.7.0 components for the latest minor version (1.7.8), everything works fine a part from Heapster. There's no way to get the Dashboard to display anything, and I can't see any useful message in logs. What could it be?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/cookeem/kubeadm-ha/issues/5, or mute the thread https://github.com/notifications/unsubscribe-auth/AF8XW8jDBUgbHEZH7Hij_LyBuATzUxsiks5sthRmgaJpZM4P93qw.

[vide]

@mottycruz I'm already using Heapster 1.3.0 (it's the same version in the howto)

# kubectl describe pod --namespace=kube-system  heapster-2216641391-4n9ch 
Name:           heapster-2216641391-4n9ch
Namespace:      kube-system
Node:           kube-master01.billy.preprod/192.168.40.41
Start Time:     Tue, 17 Oct 2017 14:28:46 +0200
Labels:         k8s-app=heapster
                pod-template-hash=2216641391
                task=monitoring
Annotations:    kubernetes.io/created-by={"kind":"SerializedReference","apiVersion":"v1","reference":{"kind":"ReplicaSet","namespace":"kube-system","name":"heapster-2216641391","uid":"b87a0df6-b336-11e7-b729-001a4a16...
Status:         Running
IP:             10.244.0.28
Created By:     ReplicaSet/heapster-2216641391
Controlled By:  ReplicaSet/heapster-2216641391
Containers:
  heapster:
    Container ID:  docker://5600a3dc0647411cba57878ed5185b59bbc66a4203397c7592dcb7d8e465e738
    Image:         gcr.io/google_containers/heapster-amd64:v1.3.0
    Image ID:      docker-pullable://gcr.io/google_containers/heapster-amd64@sha256:3dff9b2425a196aa51df0cebde0f8b427388425ba84568721acf416fa003cd5c
    Port:          <none>
    Command:
      /heapster
      --source=kubernetes:https://kubernetes.default
      --sink=influxdb:http://monitoring-influxdb.kube-system.svc:8086
    State:          Running
      Started:      Wed, 18 Oct 2017 10:34:26 +0200
    Last State:     Terminated
      Reason:       Error
      Exit Code:    2
      Started:      Wed, 18 Oct 2017 10:33:40 +0200
      Finished:     Wed, 18 Oct 2017 10:33:45 +0200
    Ready:          True
    Restart Count:  5
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from heapster-token-8zck9 (ro)
Conditions:
  Type           Status
  Initialized    True 
  Ready          True 
  PodScheduled   True 
Volumes:
  heapster-token-8zck9:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  heapster-token-8zck9
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     beta.kubernetes.io/arch=arm:NoSchedule
                 beta.kubernetes.io/arch=arm64:NoSchedule
                 beta.kubernetes.io/arch=arm:NoSchedule
                 beta.kubernetes.io/arch=arm64:NoSchedule
                 node.alpha.kubernetes.io/notReady:NoExecute for 300s
                 node.alpha.kubernetes.io/unreachable:NoExecute for 300s
Events:          <none>

[vide]

Uooops, don't know what happened but I've just checked the dashboard and it shows data...yesterday when I deployed the cluster wasn't showing a thing. Sorry for the noise.