Node log query

[aravindhp]

Enhancement Description

• Add a kubelet API for viewing logs of system services on nodes

• Kubernetes Enhancement Proposal: KEP-2258: Node log query

• Discussion Link: https://kubernetes.slack.com/archives/C0SJ4AFB7/p1610055846236600

• Primary contact (assignee): @aravindhp

• Responsible SIGs: sig-windows

• Enhancement target (which target equals to which milestone):

  • Alpha release target (x.y): 1.27
  • Beta release target (x.y): 1.30
  • Stable release target (x.y): 1.36

• Alpha

  • KEP (k/enhancements) update PR(s): KEP 2258: Node service log viewer #2271
  • Code (k/k) update PR(s):
    • KEP 2258: add node log query kubernetes#96120
  • Docs (k/website) update PR(s): KEP-2258: Node log query documentation website#40003

• Beta

  • KEP (k/enhancements) update PR(s): KEP-2258: Promote NodeLogQuery to beta #4480
  • Code (k/k) update PR(s):
    • Fix systemd unit string matches kubernetes#120678
    • test: Fix NodeLogQuery tests kubernetes#121707
    • e2e: only select linux nodes for NodeLogQuery tests kubernetes#122240
    • e2e: add NodeLogQuery tests for Windows nodes kubernetes#122594
    • features: promote NodeLogQuery to beta kubernetes#123205
  • Docs:
    • KEP-2258: Promote NodeLogQuery to beta website#45126
  • kubectl plugin: kubectl-node-logs

• Stable

  • KEP (k/enhancements) update PR(s): KEP-2258: Node log query promotion to stable (GA) #5874
  • Code (k/k) update PR(s): [FeatureGate] Promote NodeLogQuery to GA in v1.36 and lock default to true kubernetes#137544
  • Docs (k/website) update(s): KEP-2258: Update Node log query documentation for GA in v1.36 website#54487

[aravindhp]

/cc @LorbusChris @marosset @immuzz
/sig windows

[dougsland]

/cc

[annajung]

Hi @aravindhp

Enhancements Freeze is 2 days away, Feb 9th EOD PST

Enhancements team is aware that KEP update is currently in progress (PR #2271). Please make sure PR merges before the freeze. For PRR related questions or to boost the PR for PRR review, please reach out in slack #prod-readiness

Any enhancements that do not complete the following requirements by the freeze will require an exception.

• [IN PROGRESS] The KEP must be merged in an implementable state
• [IN PROGRESS] The KEP must have test plans
• [IN PROGRESS] The KEP must have graduation criteria
• [IN PROGRESS] The KEP must have a production readiness review

[aravindhp]

@annajung #2271 has the following completed:
[IN PROGRESS] The KEP must have test plans
[IN PROGRESS] The KEP must have graduation criteria
[IN PROGRESS] The KEP must have a production readiness review (I need update the check mark but it has been /approved for PRR)
Is there a reason for it to be marked IN PROGRESS?

[annajung]

@aravindhp We consider it in progress until PR merges. Even if you have a PR open for the change, if it doesn't merge before the enhancements freeze, this enhancement is at risk of not making it into the release.

[aravindhp]

Thanks for the clarification @annajung. We are waiting for LGTMs from sig-node and sig-auth to merge.

[annajung]

Hi @aravindhp,

Enhancements Freeze is now in effect.

Unfortunately, your KEP needed to be updated and the PR has not yet merged. If you wish to be included in the 1.21 Release, please submit an Exception Request as soon as possible.

/milestone clear