-
Notifications
You must be signed in to change notification settings - Fork 706
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
Fail to init aws cluster with the message "could not init cloud provider "aws": error finding instance ... timeout #2359
Comments
hello, kubeadm seems to be doing its job to pass the flags to the components that need them, so this doesn't look like a kubeadm issue. also note that the kubeadm team does not have e2e signal for any of the legacy (non- this guide on the web seem to suggest that what you are doing is valid for AWS:
this looks like a connectivity issue on the side of the kubelet. before logging a ticket in kubernetes/kubernetes about this and tagging it with thanks |
@neolit123: 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 keywords did you search in kubeadm issues before filing this one?
could not init cloud provider
kubeadm init --cloud-provider aws
Is this a BUG REPORT or FEATURE REQUEST?
BUG REPORT
Versions
kubeadm version: v1.19.4
Environment:
config file:
What happened?
sudo kubeadm init --config=kubeadm.yaml -v=5 > ./kubeadm-run.txt 2>&1
kubeadm will never fully initialize. the output shows
and
journalctl -xeu kubelet
showsconfigs in
/etc/manifests/
contains env settings with proxy variables.While from terminal with same proxy settings the
curl -v https://ec2.us-east-1.amazonaws.com/
does not timeout and returns data.What you expected to happen?
I would expect kubeadm init --cloud-provider aws to successfully complete.
How to reproduce it (as minimally and precisely as possible)?
Anything else we need to know?
It's entirely private VPC
The text was updated successfully, but these errors were encountered: