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
Kubelet fails to start with 6443: connection refused, kubeadm 1.16, Ubuntu 18.04. #82988
Comments
|
|
/sig node |
@nitkon , you can try this:
|
if you are running on openstack or any cloud please make sure to allow the ports in security groups in my case this was the error |
I also added
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
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. |
What happened:
What you expected to happen:
kubernetes installs successfully.
How to reproduce it (as minimally and precisely as possible):
Use the above kubeadm command on Ubuntu 1804 with crio as the CRI
Anything else we need to know?:
kubectl version
):BareMetal Server.
cat /etc/os-release
):uname -a
):kubeadm
CNI: calico 1.15
Kubelet logs:
The text was updated successfully, but these errors were encountered: