anchor.diff:  
   === Grafana dashboard
   
  -Grafana dashboard, accessible at http://localhost:8001/api/v1/namespaces/default/services/grafana/proxy/, now shows the information about the cluster. 
  +Grafana dashboard, accessible at http://localhost:8001/api/v1/proxy/namespaces/default/services/grafana/, now shows the information about the cluster.
   
   NOTE: Grafana dashboard will not be available if Kubernetes proxy is not running. If not running, then it can be started with the command `kubectl proxy`.
   
  
positive.code: 
  image::kubernetes-dashboard-default.png[]
  
  Click on `Nodes` to see a textual representation about the nodes running in the cluster:
  
  image::monitoring-nodes-before.png[]
  
  Install a Java application as explained in link:../helm[Deploying applications using Kubernetes Helm charts].
  
  Click on `Pods`, again to see a textual representation about the pods running in the cluster:
  
  image::monitoring-pods-before.png[]
  
  This will change after Heapster, InfluxDB and Grafana are installed.
  
  == Heapster, InfluxDB and Grafana
  
  https://github.com/kubernetes/heapster[Heapster] is a metrics aggregator and processor. It is installed as a cluster-wide pod. It gathers monitoring and events data for all containers on each node by talking to the Kubelet. Kubelet itself fetches this data from https://github.com/google/cadvisor[cAdvisor]. This data is persisted in a time series database https://github.com/influxdata/influxdb[InfluxDB] for storage. The data is then visualized using a using http://grafana.org/[Grafana] dashboard or can be viewed in Kubernetes Dashboard.
  
  Heapster collects and interprets various signals like compute resource usage, lifecycle events, etc, and exports cluster metrics via REST endpoints.
  
  Heapster, InfluxDB and Grafana are http://kubernetes.io/docs/admin/addons/[Kubernetes addons].
  
  
negative.code: ttl-controller-token-vbnhf               kubernetes.io/service-account-token   3         3h
  ```
  
  We can login using any secret with type 'kubernetes.io/service-account-token', though each of them have different privileges. In our case, we'll use the token from secret `default-token-7vh0x` to login. Use the following command to get the token for this secret:
  
      kubectl -n kube-system describe secret default-token-7vh0x
  
  Note you'll need to replace `default-token-7vh0x` with the default-token from your output list.
  
  It shows the output:
  
  