Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to connect to the server: i/o timeout after Cilium installation #32208

Open
2 of 3 tasks
alifiroozi80 opened this issue Apr 28, 2024 · 1 comment
Open
2 of 3 tasks
Labels
kind/bug This is a bug in the Cilium logic. kind/community-report This was reported by a user in the Cilium community, eg via Slack. need-more-info More information is required to further debug or fix the issue. needs/triage This issue requires triaging to establish severity and next steps.

Comments

@alifiroozi80
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

What happened?

Hello there.
I've initialized a bare-metal cluster with kubeadm. I want kube-proxy, and I deploy that as well, and everything is good.
I tried to install Cilium as my CNI only (not a replacement of kube-proxy), and after running the below command:

cilium install --version 1.15.4

After deployment of all Pods, now nothing works and kubectl commands return the below error:

$ kubectl get pod -A
Unable to connect to the server: dial tcp 10.0.7.122:6443: i/o timeout

Even the cilium status command not working.

Cilium Version

$ cilium version --client
cilium-cli: v0.16.5 compiled with go1.22.2 on linux/amd64
cilium image (default): v1.15.4
cilium image (stable): v1.15.4

Kernel Version

$ uname -a
Linux master-1 5.15.0-89-generic #99-Ubuntu SMP Mon Oct 30 20:42:41 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Kubernetes Version

1.30.0

Regression

No response

Sysdump

No response

Relevant log output

No response

Anything else?

No response

Cilium Users Document

  • Are you a user of Cilium? Please add yourself to the Users doc

Code of Conduct

  • I agree to follow this project's Code of Conduct
@alifiroozi80 alifiroozi80 added kind/bug This is a bug in the Cilium logic. kind/community-report This was reported by a user in the Cilium community, eg via Slack. needs/triage This issue requires triaging to establish severity and next steps. labels Apr 28, 2024
@youngnick youngnick added the need-more-info More information is required to further debug or fix the issue. label Apr 30, 2024
@youngnick
Copy link
Contributor

Thanks for this issue @alifiroozi80. Did you follow the steps in https://docs.cilium.io/en/stable/installation/k8s-install-kubeadm/ ?

That looks like your kubectl is unable to connect to the apiserver, which could be caused by many issues, not all of them related to Cilium. Without further info, I don't think we will be able to help you, sorry. (And obviously, if you can't connect to the cluster, I understand it will be difficult to collect further info).

I'd suggest starting over following the directions in the docs, and come back here if there are still problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug This is a bug in the Cilium logic. kind/community-report This was reported by a user in the Cilium community, eg via Slack. need-more-info More information is required to further debug or fix the issue. needs/triage This issue requires triaging to establish severity and next steps.
Projects
None yet
Development

No branches or pull requests

2 participants