search

kubernetes / website

Kubernetes website and documentation repo:
https://kubernetes.io
Creative Commons Attribution 4.0 International
4.44k stars 14.28k forks source link

Inadequate troubleshooting guidance for `kubectl cluster-info` error in 'Install and Set Up kubectl on Linux' page #43894

Closed jaleshdikshit closed 1 month ago

jaleshdikshit commented 10 months ago

What happened?

Verify kubectl configuration, while installing kubernetes with 'Install kubectl binary with curl on Linux' as mentioned on url https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/#verify-kubectl-configuration, the command kubectl cluster-info does come out with The connection to the server was refused - did you specify the right host or port?

There is no documentation on how to correct it or if there are any pre-installation configuration prerequisites required.

What did you expect to happen?

No errors

How can we reproduce it (as minimally and precisely as possible)?

'Install kubectl binary with curl on Linux' as mentioned on url https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/#verify-kubectl-configuration, the command kubectl cluster-info

Anything else we need to know?

Nothing

Kubernetes version

latest ```console $ kubectl version # paste output here ```

Cloud provider

None installing from kubernetes.io on ubuntu 22

OS version

ubuntu latest ```console # On Linux: $ cat /etc/os-release # paste output here $ uname -a # paste output here # On Windows: C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture # paste output here ```

Install tools

curl

Container runtime (CRI) and version (if applicable)

None, only dockers latest version is installed on machine

Related plugins (CNI, CSI, ...) and versions (if applicable)

No plugins on machine, it is a fresh hypervisor ubuntu linux on windows11
k8s-ci-robot commented 10 months ago

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

Please see the group list for a listing of the SIGs, working groups, and committees available.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
k8s-ci-robot commented 10 months ago

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
dims commented 10 months ago

/transfer website

kumarankit999 commented 10 months ago

/assign

aj11anuj commented 10 months ago

/language en /sig docs /priority awaiting-more-evidence

jaleshdikshit commented 9 months ago

it is fresh ubuntu virtual machine on windows 11 hyper-v, latest cubectl installed, attached is screen.

On Sat, Nov 11, 2023 at 8:47 PM ANKIT KUMAR @.***> wrote:

/assign

— Reply to this email directly, view it on GitHub https://github.com/kubernetes/website/issues/43894#issuecomment-1807001959, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATAH6GHZRWCFMRLZEF77VO3YEBIHFAVCNFSM6AAAAAA7HWXYN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBXGAYDCOJVHE . You are receiving this because you authored the thread.Message ID: @.***>

dipesh-rawat commented 9 months ago

/retitle Inadequate troubleshooting guidance for kubectl cluster-info error in 'Install and Set Up kubectl on Linux' page

jaleshdikshit commented 9 months ago

Running copy of kube-up.sh fails, sudo ./kube-up.sh ./kube-up.sh: line 33: ./../cluster/kube-util.sh: No such file of directory

k8s-triage-robot commented 6 months ago

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

This bot triages un-triaged issues according to the following rules:

You can:

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

/lifecycle stale

vaibhav2107 commented 6 months ago

/remove-lifecycle stale

k8s-triage-robot commented 3 months ago

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

This bot triages un-triaged issues according to the following rules:

You can:

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

/lifecycle stale

k8s-triage-robot commented 2 months ago

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

This bot triages un-triaged issues according to the following rules:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 1 month ago

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

This bot triages issues according to the following rules:

You can:

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

/close not-planned

k8s-ci-robot commented 1 month ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/website/issues/43894#issuecomment-2225350866): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues 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: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.