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

v1.10 known issues / FAQ accumulator #59764

Closed
krzyzacy opened this issue Feb 12, 2018 · 27 comments
Closed

v1.10 known issues / FAQ accumulator #59764

krzyzacy opened this issue Feb 12, 2018 · 27 comments
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/release Categorizes an issue or PR as relevant to SIG Release.
Milestone

Comments

@krzyzacy
Copy link
Member

Please link to this issue or comment on this issue with known errata for the 1.10.x release. This follows what we have done for prior releases.

We will be populating the "Known Issues" section of 1.10.0 and above release notes based on this issue

cc @jdumars @calebamiles @jberkus
cc @kubernetes/kubernetes-release-managers

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Feb 12, 2018
@krzyzacy
Copy link
Member Author

/sig release

@k8s-ci-robot k8s-ci-robot added sig/release Categorizes an issue or PR as relevant to SIG Release. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Feb 12, 2018
@jdumars jdumars added this to the v1.10 milestone Feb 13, 2018
@jdumars jdumars added approved-for-milestone priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Feb 13, 2018
@jdumars
Copy link
Member

jdumars commented Feb 13, 2018

Is this part of the release process documented somewhere?

@krzyzacy
Copy link
Member Author

cc @spiffxp
I was referencing #53004 and made one for 1.10

@jberkus
Copy link

jberkus commented Feb 13, 2018

There's two CRI changes which break backwards compatibility for some users:

#59475

#58973

@jberkus
Copy link

jberkus commented Feb 19, 2018

adding kind

/kind design

@jberkus
Copy link

jberkus commented Mar 2, 2018

Adjusting labels to keep this tracker in the milestone.

/kind cleanup
/remove-kind design
/priority critical-urgent
/remove-priority important-soon

@jberkus jberkus closed this as completed Mar 2, 2018
@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. and removed kind/design Categorizes issue or PR as related to design. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Mar 2, 2018
@jberkus jberkus reopened this Mar 2, 2018
@krzyzacy
Copy link
Member Author

krzyzacy commented Mar 4, 2018

(seems this issue is not as useful and not documented as part of release process, I'll just close it, but feel free to reopen if necessary)

@jberkus
Copy link

jberkus commented Mar 13, 2018

#60764
Known issue, downgrade extra steps with PVC

@Bradamant3
Copy link

Clarification, please? Do y'all want a relnote for #60933?

@Bradamant3
Copy link

Add #60764 plus related doc kubernetes/website#7731

@jberkus
Copy link

jberkus commented Mar 14, 2018

Mount propagation manual steps: #61126

@jberkus
Copy link

jberkus commented Mar 14, 2018

Clarification, please? Do y'all want a relnote for #60933?

My opinion: yes.

@jdumars
Copy link
Member

jdumars commented Mar 19, 2018

ACK. In progress
ETA: 29/03/2018
Risks: The bot nagging will drive us slowly mad

@Bradamant3
Copy link

@nickchase in case it's helpful here: think you don't need to worry about #61126 bc the relnote content is in the PR (such as it is ...). BUT it might not be in the right place in the generated relnotes. It's an action required thing.

@jberkus
Copy link

jberkus commented Mar 21, 2018

We need to doc downgrading and PVC protection. TL;DR: if you have PVCs, and need to downgrade, you need to downgrade to 1.9.6, which will be released next Wednesday, and not to an earlier version of 1.9.

@Bradamant3
Copy link

Yup. @nickchase see also comment from liggitt in kubernetes/website#7731

@Bradamant3
Copy link

#61446
#61456

@nickchase let's coordinate with @msau42 about relnotes/docs. Slack discussion also.

@msau42
Copy link
Member

msau42 commented Mar 22, 2018

We also need to add those 2 known issues to 1.9, 1.8, 1.7 patch releases as well.

@msau42
Copy link
Member

msau42 commented Mar 22, 2018

The workaround for #61446 and #61456 is to not use subPath with hostPath volumes, and instead just specify the whole path in the hostPath volume.

@nickchase
Copy link
Contributor

Adding:

  • Use of subPath module with hostPath volumes can cause issues during reconstruction (#61446) and with containerized kubelets (#61456). The workaround for this issue is to specify the complete path in the hostPath volume.

@nickchase
Copy link
Contributor

Flaky timeouts while waiting for RC pods to be running in density test -- Appears to be fixed?
Controller-manager sees higher mem-usage when load test runs before density -- Does this need a Relnote?
HostPath mounts failing with "Path is not a shared or slave mount" -- Resolved with addition to "Before Upgrading" section
kubeadm: etcd certs missing in self-hosted deploy (will be fixed in point release) -- Added

@nickchase
Copy link
Contributor

Added * In large clusters (~2K nodes) scheduling logs can explode and crash the master node. (#60933)

@jberkus
Copy link

jberkus commented Mar 26, 2018

@nickchase

Yes on Controller-manager. Suggested text:

"Some users, especially those with very large clusters, may see higher memory usage by the kube-controller-manager in 1.10."

@k8s-github-robot
Copy link

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

@krzyzacy

Issue Labels
  • sig/release: 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/cleanup: Adding tests, refactoring, fixing old bugs.
Help

@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 10, 2018
@jberkus
Copy link

jberkus commented Jul 11, 2018

/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Development

No branches or pull requests

9 participants