Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
kubeadm : fix-kubeadm-upgrade-12-13-14 #75956
What type of PR is this?
What this PR does / why we need it:
This happened because the upgrade v1.12 to v1.13, didn't change the etcd manifest because the etcd version didn't change
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fabriziopandini
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing
mauilion left a comment •
a couple of nits. Looks good.
I think we should state in the kubeadm output that this means that the etcd node will be bound to an exeternal ip address and that the user should take this into account.
Apr 2, 2019
After I set the IP from the Master-Node manually in the manifest:
I get an other error: error syncing endpoints with etc: context deadline exceeded
Does this hotfix solve this problem also?
@runam0K your hotfix is not enough for solving the problem; please refer to the issue where a possible manual hotfix is described; if you want to propose/discuss an alternative approach, it would be great if you move the discussion there for better discoverability