1.14 Release Notes: "Known Issues"

[onyiny-ang]

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

/assign @dstrebel @jeefy @onyiny-ang @alenkacz

/sig release
/milestone v1.14

[k8s-ci-robot]

@onyiny-ang: You must be a member of the kubernetes/kubernetes-milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility.

In response to this:

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

/assign @dstrebel @jeefy @onyiny-ang @alenkacz

/sig release
/milestone v1.14

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

@onyiny-ang: GitHub didn't allow me to assign the following users: alenkacz.

Note that only kubernetes members and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

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

/assign @dstrebel @jeefy @onyiny-ang @alenkacz

/sig release
/milestone v1.14

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[spiffxp]

/milestone v1.14
We're entering burndown and this looks relevant to the 1.14 release. Please /milestone clear if I am incorrect

[spiffxp]

/kind documentation

[fturib]

@chrisohaver : can you add here a comment about the known issue coredns/coredns#2629 ? Thanks!

[chrisohaver]

There is a known issue (coredns/coredns#2629) in CoreDNS 1.3.1, wherein if the Kubernetes API shuts down while CoreDNS is connected, CoreDNS will crash. The issue is fixed in CoreDNS 1.4.0 in coredns/coredns#2529.

Let me know if more detail is needed.

[fturib]

workaround for this issue would be to use another version of CoreDNS : 1.3.0, or 1.4.0.
Another possible solution is to mount an EmptyDir volume to /tmp.

[BenTheElder]

FYI a working CoreDNS issue link is at coredns/coredns#2629 and fix link at coredns/coredns#2529

[clkao]

kubelet might fail to restart if an existing flexvolume mounted pvc contains large number of directories, or is full. #75019

[rochacon]

The v1.14.0 release notes misses a note on apiserver --enable-swagger-ui flag removal. API server 1.14 will fail to start if the flag is present.

Ref: 9229399

[fejta-bot]

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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

[BenTheElder]

@justaugustus is there something we should be doing here?

[onyiny-ang]

@BenTheElder @justaugustus These are created to catch known issues prior to the release so that they can be included in the release notes. The only reason I haven't closed this is because I am not sure whether or not it is useful for users to keep the issue open once the release has been cut--since other "known issues" may arise. If not, I'm happy to close this as well as the issue for 1.15.

[spiffxp]

/remove-lifecycle rotten
/close
I looked back at other "known issues" issues going back to 1.9 and they never stayed open long enough to hit rotten. Most were usually open / active for roughly a month, which I suspect lines up with when a patch release or two had been cut. I think we can call this done.

[k8s-ci-robot]

@spiffxp: Closing this issue.

In response to this:

/remove-lifecycle rotten
/close
I looked back at other "known issues" issues going back to 1.9 and they never stayed open long enough to hit rotten. Most were usually open / active for roughly a month, which I suspect lines up with when a patch release or two had been cut. I think we can call this done.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[BenTheElder]

Makes sense! Thanks 😅