kubernetes / kubernetes/kubectl

Improve default kubectl behavior when it doesn't know what cluster to talk to

Open
#1,340 27 comments 0 reactions 1 assignee Claimed by @indevi View on GitHub
area/kubectl area/usability lifecycle/frozen needs-triage priority/important-soon sig/cli
Dominant language
Go
Stars
3.3k
Forks
1k
PR merge metrics
No merged PRs in 30d

Description

At minimum, we need to improve the error message:
`The connection to the server localhost:8080 was refused - did you specify the right host or port?`

We might also want to consider not using localhost as the default, though we want to keep it aligned with our single-node dev cluster plans. kubernetes/kubernetes#24106

cc @kubernetes/kubectl @dlorenc @vishh

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.