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

1.13 Release Notes: "Known Issues" #70955

Closed
marpaia opened this Issue Nov 12, 2018 · 15 comments

Comments

Projects
None yet
7 participants
@marpaia
Copy link
Member

commented Nov 12, 2018

This issue is a bucket placeholder for collaborating on the "Known Issues" additions for the 1.13 Release Notes. If you know of issues or API changes that are going out in 1.13, please comment here so that we can coordinate incorporating information about these changes in the Release Notes.

/assign @marpaia

/sig release
/milestone v1.13

@AishSundar

This comment has been minimized.

Copy link
Contributor

commented Nov 15, 2018

/milestone v1.13

@k8s-ci-robot k8s-ci-robot added this to the v1.13 milestone Nov 15, 2018

@AishSundar

This comment has been minimized.

Copy link
Contributor

commented Nov 15, 2018

@saad-ali @msau42 This is an umbrella issue to gather list of known issues and workaound in 1.13. Can you please add the note and workaround for #70716 (promoting GCE RePD support to GA in Kubernetes) discussed in the email thread offline. Thanks

@AishSundar

This comment has been minimized.

Copy link
Contributor

commented Nov 15, 2018

1 more item to followup for release notes and/or known issue - #71020 (review)

@msau42

This comment has been minimized.

Copy link
Member

commented Nov 15, 2018

cc @verult for documenting known repd naming issue

@AishSundar

This comment has been minimized.

Copy link
Contributor

commented Nov 19, 2018

As mentioned in #71020 's release notes section, CSI is intentionally not backwards compatible between 1.12 and 1.13. xref: #65246 (comment)

@liggitt

This comment has been minimized.

Copy link
Member

commented Nov 24, 2018

CSI compatibility issue above was resolved in beta.2

@AishSundar

This comment has been minimized.

Copy link
Contributor

commented Nov 27, 2018

One more known issue related to CSI raciness - #71440 (comment)

@saad-ali

This comment has been minimized.

Copy link
Member

commented Nov 28, 2018

Also, flex volume resize issue: #71470

@AishSundar

This comment has been minimized.

Copy link
Contributor

commented Nov 28, 2018

Also CSI driver registartion latency - #71383 (comment)

@saad-ali ^^

@saad-ali

This comment has been minimized.

Copy link
Member

commented Nov 28, 2018

Also CSI driver registartion latency - #71383 (comment)

This issue is an caused by an external sidecar container (driver-registrar). Once it is fixed on the external sidecar, the issue will not exist with 1.13.0. So it does not make sense to capture it in Kubernetes release notes.

Instead the release notes for the external-container should capture this (I'll take care of that).

@saad-ali

This comment has been minimized.

Copy link
Member

commented Nov 28, 2018

One more known issue related to CSI raciness - #71440 (comment)

This is not actually a raciness issue. Regardless, the actual issue from 71440 is already captured in the release notes under if kubelet plugin registration for a driver fails, kubelet will not retry...

@marpaia

This comment has been minimized.

Copy link
Member Author

commented Nov 28, 2018

So, thanks to @saad-ali, CSI raciness is represented in the notes and CSI driver registration latency does not require a known issue note.

In working with @gnufied, he came up with this note, which I've added to the known issues section of the doc:

In come cases, a PVC may have erroneous Resizing condition even after volume has been successfully expanded. Users may choose to delete the condition, but it is not required.

@saad-ali

This comment has been minimized.

Copy link
Member

commented Nov 28, 2018

In come cases, a PVC may have erroneous Resizing condition even after volume has been successfully expanded. Users may choose to delete the condition, but it is not required.

LGTM

@marpaia

This comment has been minimized.

Copy link
Member Author

commented Nov 28, 2018

All known issues up until this point are represented in the PR for the "final" release notes doc here: kubernetes/sig-release#386

@fejta-bot

This comment has been minimized.

Copy link

commented Feb 26, 2019

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.