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.14 Release Notes: "Known Issues" #74425

Open
onyiny-ang opened this Issue Feb 22, 2019 · 10 comments

Comments

@onyiny-ang
Copy link

onyiny-ang commented Feb 22, 2019

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

This comment has been minimized.

Copy link
Contributor

k8s-ci-robot commented Feb 22, 2019

@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

This comment has been minimized.

Copy link
Contributor

k8s-ci-robot commented Feb 22, 2019

@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

This comment has been minimized.

Copy link
Member

spiffxp commented Feb 24, 2019

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

@k8s-ci-robot k8s-ci-robot added this to the v1.14 milestone Feb 24, 2019

@spiffxp

This comment has been minimized.

Copy link
Member

spiffxp commented Mar 18, 2019

/kind documentation

@fturib

This comment has been minimized.

Copy link
Contributor

fturib commented Mar 18, 2019

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

@chrisohaver

This comment has been minimized.

Copy link
Contributor

chrisohaver commented Mar 18, 2019

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

This comment has been minimized.

Copy link
Contributor

fturib commented Mar 20, 2019

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

This comment has been minimized.

Copy link
Member

BenTheElder commented Mar 20, 2019

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

@clkao

This comment has been minimized.

Copy link
Contributor

clkao commented Mar 21, 2019

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

@rochacon

This comment has been minimized.

Copy link

rochacon commented Mar 26, 2019

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

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.