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

kubeadm v1.10 release tracking issue #60608

Closed
timothysc opened this Issue Mar 1, 2018 · 11 comments

Comments

@timothysc
Member

timothysc commented Mar 1, 2018

In following with history we will be curating action items here, but it's still a WIP, atm: https://github.com/kubernetes/kubeadm/milestone/5

All non-bug-fixes for this release cycle should be merged, but there is still an ongoing list of bugs that folks may execute against for the remainder of the freeze and we will evaluating on a case-by-case basis.

/cc @detiber @jdumars @roberthbailey @kubernetes/kubernetes-release-managers @luxas @kubernetes/sig-cluster-lifecycle-misc

@jdumars

This comment has been minimized.

Member

jdumars commented Mar 1, 2018

Thank you for creating this issue!

@idvoretskyi

This comment has been minimized.

Member

idvoretskyi commented Mar 3, 2018

/cc

@jberkus

This comment has been minimized.

jberkus commented Mar 5, 2018

@timothysc

Adding required tags.

Please use this issue to supply a frequent summary update of the issues you are tracking in the kubeadm repo and their status. Especially, please call out and link to any bugs that are blockers for 1.10.

/kind feature
/priority critical-urgent

@jberkus

This comment has been minimized.

jberkus commented Mar 12, 2018

@timothysc, @luxas can we have a general status update on the kubeadm issues? The issues themselves don't generally have status updates. This is the last week before release, where are you with the kubeadm changes?

@timothysc

This comment has been minimized.

Member

timothysc commented Mar 13, 2018

@jberkus

We're all green except for the 1.9-1.10 upgrade tests which appear to have other issues that are not kubeadm specific.

Final default update PR is #61127 which will auto-close this issue.

@timothysc

This comment has been minimized.

Member

timothysc commented Mar 13, 2018

^ I don't know why we have this policy but it's ridiculous... @kubernetes/sig-contributor-experience-bugs

@jberkus

This comment has been minimized.

jberkus commented Mar 13, 2018

@timothysc are there any 1.9-1.10 upgrade issues which aren't already represented by issues against kubernetes/kubernetes? that is, are there any in the kubadm repo only?

@timothysc

This comment has been minimized.

Member

timothysc commented Mar 14, 2018

Not that I see atm, I still need to triage the inbound issues.

@jdumars

This comment has been minimized.

Member

jdumars commented Mar 14, 2018

/status in-progress

@jdumars

This comment has been minimized.

Member

jdumars commented Mar 18, 2018

/status in-progress

@k8s-merge-robot

This comment has been minimized.

Contributor

k8s-merge-robot commented Mar 18, 2018

[MILESTONENOTIFIER] Milestone Issue: Up-to-date for process

@roberthbailey @timothysc

Note: This issue is marked as priority/critical-urgent, and must be updated every 1 day during code freeze.

Example update:

ACK.  In progress
ETA: DD/MM/YYYY
Risks: Complicated fix required
Issue Labels
  • sig/cluster-lifecycle: Issue will be escalated to these SIGs if needed.
  • priority/critical-urgent: Never automatically move issue out of a release milestone; continually escalate to contributor and SIG through all available channels.
  • kind/feature: New functionality.
Help

k8s-merge-robot added a commit that referenced this issue Mar 19, 2018

Merge pull request #61127 from timothysc/kubeadm-1.10
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>.

Updates kubeadm default to use 1.10

**What this PR does / why we need it**:
In line with https://github.com/kubernetes/kubeadm/blob/master/docs/release-cycle.md, the default branch for kubeadm to deploy should be bumped right before the rc.1.
This can even be manually merged by the someone from the release team.

**Which issue(s) this PR fixes** :
Fixes #60608 

**Special notes for your reviewer**:

**Release note**:

```
Updates default deployment for kubeadm to 1.10 
```

/cc @kubernetes/sig-cluster-lifecycle-pr-reviews @kubernetes/sig-release-members  @dims @jberkus @jdumars
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment