heapster | Compute Resource Usage Analysis and Monitoring of Container | Monitoring library

It looks like the kubernetes-dashboard's serviceaccount doesn't have access to all kubernetes resources (in particular, it can't access the metric server service).

To fix this you should create a new ServiceAccount for the dashboard and give it more permissions.

Here's one that I found on another similar post (be careful since it will give admin privileges to the dashboard, and whoever uses it will be able to destroy/create new or existing resources on your kubernetes cluster):

Looks like you created the secret my-secret in default namespace but the deployment app-config-service is running in kube-system namespace and hence can not refer to my-secret using imagePullSecrets. Creating the secret my-secret in kube-system namespace should solve the issue.

Check version of kubectl using kubectl version

From kubectl 1.18 version kubectl run creates only pod and nothing else. To create a deployment use kubectl create deployment or use older version of kubectl

This is because pods such as kube proxy , Fluentd, Prometheus are running in host network directly via hostNetwork: true. You can describe those pods and verify that hostNetwork: true is present.

Now coming to the point why these pods need to run in host network in the first place , kube proxy needs access to host's IP tables, prometheus collects metrics and Fluentd collects logs from the host system.

You can just deploy a sample pod such as nginx with hostNetwork: true and it will get node IP.If you remove hostNetwork: true it will get IP from pod CIDR range.

Nothing is frozen - the command for port-forward is running in the foreground. If you have setup the service properly with the right port number everything should be working fine.

Try running the same as a background process, by adding & at the end.

microk8s kubectl port-forward -n kube-system service/kubernetes-dashboard 10443:443 &

If you want to kill it. Get the pid

ps -aef

and then kill it using the below command

kill -9 pid-here

After experimenting all day...

I came with a solution, it's not the best or straight forward but at least it's working. My slave is connected! INFO: Connected

So, I edited the jenkins-agent service and from type: ClusterIP I changed to type: LoadBalancer. That gave me a new fresh loadbalancer and after I decided to add the port 8080 because in the service yaml file it's using the same selector as in jenkins service.

(jenkins-agent service yaml)

What you're looking for is application & infrastructure specific metrics. For this, the TICK stack could be helpful! Specifically Telegraf can be set up to gather detailed infrastructure metrics like Memory- and CPU pressure or even the resources used by individual docker containers, network and IO metrics etc... But it can also scrape Prometheus metrics from pods. These metrics are then shipped to influxdb and visualized using either chronograph or grafana.

You can try kubectl describe deploy monitoring-influxdb to get some high-level view of the deployment, maybe some information here.

For more detailed logs, first get the pods: kubectl get po Then, request the pod logs: kubectl logs

if you use deployments, for sake of human operators you'll find your pods names as -<[0-9a-z]{5}> where replicaset is -. For kubernetes it self, naming of pods is irrelevant.