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

Known issues for kubernetes 1.2 release #21000

Closed
dchen1107 opened this issue Feb 10, 2016 · 7 comments
Closed

Known issues for kubernetes 1.2 release #21000

dchen1107 opened this issue Feb 10, 2016 · 7 comments
Assignees
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@dchen1107
Copy link
Member

It is the time to collect all known issues for our coming release now.

cc/ @thockin @bgrant0607 @davidopp @lavalamp @roberthbailey

@dchen1107 dchen1107 added this to the v1.2 milestone Feb 10, 2016
@dchen1107 dchen1107 added the kind/documentation Categorizes issue or PR as related to documentation. label Feb 10, 2016
@bgrant0607 bgrant0607 added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. area/release-eng Issues or PRs related to the Release Engineering subproject and removed team/none labels Feb 11, 2016
@bgrant0607
Copy link
Member

#16737: kubectl rolling-update can't rollback if the rollout is already stuck on maxUnavailable

@dchen1107
Copy link
Member Author

Known issues with docker 1.9.1:
#16110 (comment)

@bgrant0607
Copy link
Member

Paused deployments can't be resized and don't clean up old ReplicaSets. Fix is in progress (#20273), but didn't make it into 1.2.

@bgrant0607
Copy link
Member

The known-issues doc is very, very out of date:
http://kubernetes.github.io/docs/user-guide/known-issues/

@bgrant0607
Copy link
Member

@dchen1107 requests a separate doc for docker issues

We should also link to known issues from the release description on github

@bgrant0607
Copy link
Member

1.1 issues don't seem to be documented: #15747

@bgrant0607
Copy link
Member

I think the most important of these are in the release notes.

@bgrant0607 bgrant0607 self-assigned this Mar 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

2 participants