Lab 13.3. Adding Tools for Monitoring and Metrics

harimino

Hello,

After fetching the chart, i don't see anything relating to service in my values.yaml

Here the result of the grep on the values.yaml

harimino@cp-node:~/kubernetes-dashboard$ cat values.yaml | grep service
  serviceMonitor:

Or I should do the change on one of those file

charts/metrics-server/values.yaml
charts/ingress-nginx/values.yaml ==> I have the type here
charts/cert-manager/values.yaml

chrispokorni

Hi @harimino,

It seems the values.yaml of the latest kubernetes-dashboard charts no longer include the service configuration.

As a workaround, you can deploy the dashboard release of the kubernetes-dashboard chart, and edit the service object to update its type and, optionally, declare a desired nodeport value:

kubectl edit service dashboard-kubernetes-dashboard

Regards,
-Chris

marcossantos

Hello @chrispokorni good night!

I tried installing the dashboard charm.

helm upgrade --install metrics-server metrics-server/metrics-server

root@masternode:~# helm repo add metrics-server https://kubernetes-sigs.github.io/metrics-server/
"metrics-server" has been added to your repositories
root@masternode:~# helm upgrade --install metrics-server metrics-server/metrics-server
Release "metrics-server" does not exist. Installing it now.
E0129 22:20:46.245168 106950 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle th e request
E0129 22:20:46.250908 106950 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle th e request
E0129 22:20:46.366681 106950 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle th e request
E0129 22:20:46.386585 106950 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle th e request
E0129 22:20:46.456700 106950 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle th e request
E0129 22:20:46.460029 106950 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle th e request
E0129 22:20:46.494767 106950 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle th e request
E0129 22:20:46.530393 106950 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle th e request
E0129 22:20:46.554799 106950 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle th e request
E0129 22:20:46.594328 106950 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle th e request
E0129 22:20:46.620530 106950 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle th e request
E0129 22:20:46.674791 106950 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle th e request
E0129 22:20:46.699641 106950 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle th e request
E0129 22:20:46.744793 106950 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle th e request
E0129 22:20:46.820725 106950 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle th e request
E0129 22:20:46.838815 106950 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle th e request
E0129 22:20:46.883544 106950 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle th e request
E0129 22:20:46.934187 106950 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle th e request
E0129 22:20:47.413126 106950 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle th e request
E0129 22:20:47.465809 106950 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle th e request
Error: Unable to continue with install: ClusterRole "system:metrics-server" in namespace "" exists and cannot be imported into the current releas e: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation e rror: missing key "meta.helm.sh/release-name": must be set to "metrics-server"; annotation validation error: missing key "meta.helm.sh/release-na mespace": must be set to "default"

Git itself says that the latest versions are not being supported.

In the installation output itself it says that there are properties that need to be defined, in this case should I go to the home/.cache/helm/repository directory and change its yaml so that I can create the correct resources?

chrispokorni

Hi @marcossantos,

It seems you are using an alternative method to install the metrics-server, which has not been tested in the course lab environment.

Please use the installation approach presented in the lab guide with the additional tweaks posted in earlier forum posts.

Install the latest release of the metrics-server from its github repo as presented in step 3, then in step 5 edit the deployment with the flags recommended in this earlier comment.

Once metrics-server is up and running, install the dashboard chart as instructed in the lab guide, and read through the following comments for suggested edits:

https://forum.linuxfoundation.org/discussion/comment/38223/#Comment_38223

https://forum.linuxfoundation.org/discussion/comment/38139/#Comment_38139

Regards,
-Chris