Move frequent Kubelet heartbeats to Lease API

[mtaufen]

Feature Description

• One-line feature description (can be used as a release note): Kubelet creates and periodically renews a Lease on the node; node lifecycle controller treats this lease as a health signal
• Primary contact (assignee): @wangzhen127
• Responsible SIGs: sig-node
• Design proposal link (community repo): KEP-0009
• Link to e2e and/or unit tests: (coming soon)
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @yujuhong @dchen1107 @wojtek-t
• Approver (likely from SIG/area to which feature belongs): @yujuhong
• Feature target (which target equals to which milestone):
  • Alpha release target (1.13)
    • coordination API group merged to beta
      • Create "Lease" API in the new "coordination.k8s.io" api group kubernetes#64246
    • Kubelet creates and periodically renews Lease
      • Kubelet creates and manages node leases kubernetes#66257
    • Node controller treats Kubelet leases as a health signal
    • Re-tune Kubelet Node status updates as described in [KEP-0009]
      (https://github.com/kubernetes/community/blob/master/keps/sig-node/0009-node-heartbeat.md)
  • Beta release target (1.14)
    • Released
  • GA release target (1.17)
    • Released

[justaugustus]

@mtaufen --

It looks like this feature is currently in the Kubernetes 1.12 Milestone.

If that is still accurate, please ensure that this issue is up-to-date with ALL of the following information:

• One-line feature description (can be used as a release note):
• Primary contact (assignee):
• Responsible SIGs:
• Design proposal link (community repo):
• Link to e2e and/or unit tests:
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
• Approver (likely from SIG/area to which feature belongs):
• Feature target (which target equals to which milestone):
  • Alpha release target (x.y)
  • Beta release target (x.y)
  • Stable release target (x.y)

Set the following:

• Description
• Assignee(s)
• Labels:
  • stage/{alpha,beta,stable}
  • sig/*
  • kind/feature

Once this feature is appropriately updated, please explicitly ping @justaugustus, @kacole2, @robertsandoval, @rajendar38 to note that it is ready to be included in the Features Tracking Spreadsheet for Kubernetes 1.12.

---

Please note that the Features Freeze is July 31st, after which any incomplete Feature issues will require an Exception request to be accepted into the milestone.

In addition, please be aware of the following relevant deadlines:

• Docs deadline (open placeholder PRs): 8/21
• Test case freeze: 8/28

Please make sure all PRs for features have relevant release notes included as well.

Happy shipping!

[mtaufen]

@justaugustus this is ready to be included in the v1.12 milestone.

Thanks!

[justaugustus]

Added. Thanks for confirming, @mtaufen!

[mtaufen]

We decided to push this to 1.13, given the limited time we have left.
Additionally, @wangzhen127 is going to own this feature going forward, as I have been pulled into other work.

[mtaufen]

We will still try to merge kubernetes/kubernetes#66257 for 1.12, since it is almost done and we don't want it to rot.

[kacole2]

thanks for the update @mtaufen this has been removed from the 1.12 tracking sheet and added to the tab Removed from Milestone.

cc @justaugustus

[justaugustus]

@mtaufen -- thanks for being proactive about updating us!
@kacole2 -- thanks for getting the sheet updated

/unassign @mtaufen
/assign @wangzhen127

[wojtek-t]

I decided that we will wait for one more release to graduate to GA to get a bit more feedback about the feature.

/tracked no

[mrbobbytables]

Hey there @wojtek-t @wangzhen127 -- 1.17 Enhancements lead here. I wanted to check in and see if you think this Enhancement will be graduating to stable in 1.17?

The current release schedule is:

Monday, September 23 - Release Cycle Begins
Tuesday, October 15, EOD PST - Enhancements Freeze
Thursday, November 14, EOD PST - Code Freeze
Tuesday, November 19 - Docs must be completed and reviewed
Monday, December 9 - Kubernetes 1.17.0 Released

If you do, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

[wojtek-t]

Yes - 1.17 is the current plan for GA.

[mrbobbytables]

Awesome, thanks! I'll add it to the tracking sheet.
/stage stable

[VineethReddy02]

@wojtek-t @wangzhen127

I'm one of the v1.17 docs shadows.
Does this enhancement (or the work planned for v1.17) require any new docs (or modifications to existing docs)? If not, can you please update the 1.17 Enhancement Tracker Sheet (or let me know and I’ll do so)

If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.17) due by Friday, Nov 8th, it can just be a placeholder PR at this time. Let me know if you have any questions!

Thanks!

[wojtek-t]

Yes - it will require small docs PR to update feature status. I will send it out before deadline.

[annajung]

Hey @wojtek-t 1.17 Enhancement Shadow here! 👋 I am reaching out to check in with you to see how this enhancement is going.

The Enhancement team is looking to track k/k PRs that are related to this enhancement. I see that you have referenced this in kubernetes/kubernetes#84351 which have been added to the tracking sheet as part of this enhancement. Are there any other k/k PRs that need to be tracked as well?

Also, another friendly reminder that we're quickly approaching code freeze (Nov. 14th).

[wojtek-t]

kubernetes/kubernetes#84351
and docs PR: kubernetes/website#17189