Antti K. Koskela • 7/1/2025

Any kubectl command throws "Unhandled Error" err="couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connect: connection refused" - what do?

This article provides a troubleshooting guide for a common kubectl error where all commands fail with 'couldn't get current server API group list' and a connection refused on localhost:8080. It explains the likely cause—missing or incorrect Kubernetes cluster context—and offers a solution involving re-running Azure CLI commands to properly fetch and set cluster credentials in the correct terminal session.

0 comments

#configuration #api server #Kubernetes