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

Update default etcd version to 3.2.x in v1.10 #621

Closed
luxas opened this issue Dec 25, 2017 · 0 comments · Fixed by kubernetes/kubernetes#57230
Closed

Update default etcd version to 3.2.x in v1.10 #621

luxas opened this issue Dec 25, 2017 · 0 comments · Fixed by kubernetes/kubernetes#57230
Assignees
Labels
area/ecosystem area/upgrades priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triaged
Milestone

Comments

@luxas
Copy link
Member

luxas commented Dec 25, 2017

Same as #450, but for 3.2.12 or something for v1.10

@xiangpengzhao is on it already.
We're following the upstream k8s validated version, relevant PRs/issues: kubernetes/kubernetes#57230, kubernetes/kubernetes#57480, kubernetes/kubernetes#56114 and kubernetes/kubernetes#47131

@luxas luxas added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. area/ecosystem area/upgrades kind/enhancement labels Dec 25, 2017
@luxas luxas added this to the v1.10 milestone Dec 25, 2017
k8s-github-robot pushed a commit to kubernetes/kubernetes that referenced this issue Feb 7, 2018
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

Update kubeadm supported etcd version to 3.2.14 in 1.10

**What this PR does / why we need it**:
Kubernetes will upgrade to etcd server 3.2.14 in 1.10 cycle (#58645), update DefaultEtcdVersion in kubeadm to this version.

**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:
relevant PR: #57480 #58645
fixes: kubernetes/kubeadm#621

**Special notes for your reviewer**:
/cc @kubernetes/sig-cluster-lifecycle-pr-reviews

**Release note**:

```release-note
NONE
```
kubeadm don't need to advertise this in release notes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ecosystem area/upgrades priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants