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

failed to get APIEndpoint information for this node #71737

Closed
ygqygq2 opened this Issue Dec 5, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@ygqygq2

ygqygq2 commented Dec 5, 2018

Upgrade from v1.12.3 to v1.13.0. A master node can not upgrade. How to fix it?

[root@master3 ~]# kubeadm upgrade plan
[preflight] Running pre-flight checks.
[upgrade] Making sure the cluster is healthy:
[upgrade/config] Making sure the configuration is correct:
[upgrade/config] Reading configuration from the cluster...
[upgrade/config] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[upgrade/config] FATAL: failed to getAPIEndpoint: failed to get APIEndpoint information for this node
@k8s-ci-robot

This comment has been minimized.

Contributor

k8s-ci-robot commented Dec 5, 2018

@ygqygq2: There are no sig labels on this issue. Please add a sig label by either:

  1. mentioning a sig: @kubernetes/sig-<group-name>-<group-suffix>
    e.g., @kubernetes/sig-contributor-experience-<group-suffix> to notify the contributor experience sig, OR

  2. specifying the label manually: /sig <group-name>
    e.g., /sig scalability to apply the sig/scalability label

Note: Method 1 will trigger an email to the group. See the group list.
The <group-suffix> in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals.

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.

@ygqygq2

This comment has been minimized.

ygqygq2 commented Dec 5, 2018

I'm skip to run kubeadm upgrade apply v1.13.0, then to run the follow command:

yum upgrade -y kubelet kubeadm --disableexcludes=kubernetes
kubeadm upgrade node config --kubelet-version $(kubelet --version | cut -d ' ' -f 2)
systemctl daemon-reload
systemctl restart kubelet

Now is version v1.13.0, is that right?

@ygqygq2 ygqygq2 closed this Dec 8, 2018

@amolredhat

This comment has been minimized.

amolredhat commented Dec 10, 2018

While upgrading kubeadm we got below error. Any idea how to fix this?
I am trying to upgarde version from v1.12.2 to v1.13.0

# kubeadm upgrade plan

[preflight] Running pre-flight checks.
[upgrade] Making sure the cluster is healthy:
[upgrade/config] Making sure the configuration is correct:
[upgrade/config] Reading configuration from the cluster...
[upgrade/config] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
error syncing endpoints with etc: dial tcp etcd3:2379: connect: connection refused
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment