Welcome to the new Linux Foundation Forum!

Lab 12.3 Unable to get the metrics server to talk to the API server

Hi there,

Not sure where I'm going wrong (and I don't want to upgrade just to see if its a versioning issue).

Apart from a couple of labs which needed tweaking (new nameserver entry [Services] , wrong api [Networking]), I've not had any issues following the labs until this lab.

The metric server installs correctly but there is some confusion over the ports 443 / 4443 and I can't get the metric-server to server up metrics summary to the api server.

My set up is using two GCP-provisioned nodes (output below):

kubectl version

**Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.1", GitCommit:"d647ddbd755faf07169599a625faf302ffc34458", GitTreeState:"clean", BuildDate:"2019-10-02T17:01:15Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.1", GitCommit:"d647ddbd755faf07169599a625faf302ffc34458", GitTreeState:"clean", BuildDate:"2019-10-02T16:51:36Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
**
kubectl get nodes

NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
k8s-head Ready master 31d v1.16.1 10.154.0.11 Ubuntu 16.04.6 LTS 4.15.0-1052-gcp docker://18.9.7
k8s-worker Ready 31d v1.16.1 10.154.0.12 Ubuntu 16.04.6 LTS 4.15.0-1052-gcp docker://18.9.7

kubectl get pods --all-namespaces -o wide

NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
default taint-deployment-7cf4d757c8-6ghf2 1/1 Running 1 3d15h 192.168.193.213 k8s-head
default taint-deployment-7cf4d757c8-84sdm 1/1 Running 1 3d15h 192.168.254.181 k8s-worker
default taint-deployment-7cf4d757c8-ddpmm 1/1 Running 1 3d15h 192.168.254.190 k8s-worker
default taint-deployment-7cf4d757c8-l66h8 1/1 Running 1 3d15h 192.168.254.191 k8s-worker
default taint-deployment-7cf4d757c8-lb6gz 1/1 Running 1 3d15h 192.168.193.209 k8s-head
default taint-deployment-7cf4d757c8-q4wm9 1/1 Running 1 3d15h 192.168.254.183 k8s-worker
default taint-deployment-7cf4d757c8-ql8xt 1/1 Running 1 3d15h 192.168.254.189 k8s-worker
default taint-deployment-7cf4d757c8-tj6gv 1/1 Running 1 3d15h 192.168.193.207 k8s-head
kube-system calico-kube-controllers-6bbf58546b-m6x28 1/1 Running 1 31d 192.168.193.200 k8s-head
kube-system calico-node-64k58 1/1 Running 1 31d 10.154.0.11 k8s-head
kube-system calico-node-cglzk 1/1 Running 1 31d 10.154.0.12 k8s-worker
kube-system coredns-5644d7b6d9-fgcmd 1/1 Running 1 31d 192.168.193.201 k8s-head
kube-system coredns-5644d7b6d9-t6wpt 1/1 Running 1 31d 192.168.193.203 k8s-head
kube-system etcd-k8s-head 1/1 Running 1 31d 10.154.0.11 k8s-head
kube-system kube-apiserver-k8s-head 1/1 Running 1 31d 10.154.0.11 k8s-head
kube-system kube-controller-manager-k8s-head 1/1 Running 1 31d 10.154.0.11 k8s-head
kube-system kube-proxy-n2fvg 1/1 Running 1 31d 10.154.0.11 k8s-head
kube-system kube-proxy-nd6n2 1/1 Running 1 31d 10.154.0.12 k8s-worker
kube-system kube-scheduler-k8s-head 1/1 Running 1 31d 10.154.0.11 k8s-head
kube-system traefik-ingress-controller-779cz 1/1 Running 1 3d15h 10.154.0.12 k8s-worker
kube-system traefik-ingress-controller-bbt7v 1/1 Running 1 5d17h 10.154.0.11 k8s-head

cat kubeadm-config.yaml

apiVersion: kubeadm.k8s.io/v1beta2
kind: ClusterConfiguration
kubernetesVersion: 1.16.1
controlPlaneEndpoint: "k8smaster:6443"
networking:
podSubnet: 192.168.0.0/16

Can you help?

Sign In or Register to comment.