Metrics Server - AKS 1.20.11 - Azure Stack Hub - Error from server (ServiceUnavailable): the server is currently unable to handle the request (get nodes.metrics.k8s.io)

[zohebs341]

Hi Team,

By using aks-engine, I've deployed azure aks 1.20.11 in Azure stack hub. Metric server is up/running, however I am not getting metrics.

#kubectl top nodes Error from server (ServiceUnavailable): the server is currently unable to handle the request (get nodes.metrics.k8s.io)

Logs:

kubectl describe po metrics-server-776c59b7f9-4pjt2 -n kube-system Name: metrics-server-776c59b7f9-4pjt2 Namespace: kube-system Priority: 2000000000 Priority Class Name: system-cluster-critical Service Account: metrics-server Node: k8s-uqudoapi1-63284788-0/10.240.0.5 Start Time: Wed, 19 Oct 2022 17:08:02 +0000 Labels: k8s-app=metrics-server pod-template-hash=776c59b7f9 Annotations: kubernetes.io/psp: privileged Status: Running IP: 10.244.2.2 IPs: IP: 10.244.2.2 Controlled By: ReplicaSet/metrics-server-776c59b7f9 Containers: metrics-server: Container ID: docker://cd21ddac6d5e4a66df2a40c47b0aa4b9dccfe4f653583e72e077f07fce895f0d Image: mcr.microsoft.com/oss/kubernetes/metrics-server:v0.5.0 Image ID: docker-pullable://mcr.microsoft.com/oss/kubernetes/metrics-server@sha256:682d3a1a48abbe03df05e1084923ab668a6651fd80327f9694b0cf302cc49f90 Port: 4443/TCP Host Port: 0/TCP Args: --cert-dir=/tmp --secure-port=4443 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --kubelet-use-node-status-port --metric-resolution=15s --kubelet-insecure-tls State: Running Started: Wed, 19 Oct 2022 17:08:03 +0000 Ready: True Restart Count: 0 Requests: cpu: 100m memory: 200Mi Liveness: http-get https://:https/livez delay=0s timeout=1s period=10s #success=1 #failure=3 Readiness: http-get https://:https/readyz delay=20s timeout=1s period=10s #success=1 #failure=3 Environment: Mounts: /tmp from tmp-dir (rw) /var/run/secrets/kubernetes.io/serviceaccount from metrics-server-token-55plf (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: tmp-dir: Type: EmptyDir (a temporary directory that shares a pod's lifetime) Medium: SizeLimit: metrics-server-token-55plf: Type: Secret (a volume populated by a Secret) SecretName: metrics-server-token-55plf Optional: false QoS Class: Burstable Node-Selectors: kubernetes.io/os=linux Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s node.kubernetes.io/unreachable:NoExecute op=Exists for 300s

===============

"Failed to scrape node" err="Get "https://10.x.x.x.7:10250/stats/summary?only_cpu_and_memory=true": read tcp 10.x.x.x:52312->10.x.x.x:10250: read: connection reset by peer" node="k8s-master-63284788-2"

[yangjunmyfm192085]

metrics-server cannot access kubelet stats/summay endpoint Please make sure you can access port 10250 of kubelet normally

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[rexagod]

/close

[k8s-ci-robot]

@rexagod: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.