Split stdout and stderr log stream of container

[knight42]

Enhancement Description

• One-line enhancement description (can be used as a release note): Split stdout and stderr log stream of container
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3288-separate-stdout-from-stderr
• Discussion Link: kubectl logs should allow to discriminate between pod's stderr and stdout kubernetes#28167
• Primary contact (assignee): @knight42
• Responsible SIGs: sig-node, sig-apimachinery, sig-cli
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.32
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP 3288: Split stdout and stderr log stream #3289
    • feat: update kep 3288 #4879
  • Code (k/k) update PR(s):
    • API: add a new Stream field to PodLogOptions kubernetes#127360
    • feat(kubectl): print the logs from given log sream kubernetes#128159 (not required for 1.32)
    • feat: retrieve specific log stream of a container kubernetes-sigs/cri-tools#1724
  • Docs (k/website) update PR(s):
    • Update docs for split stdout / stderr Pod logging website#48405
    • blog: PodLogsSplitStreams announcement website#48598

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[knight42]

/sig node
/sig api-machinery
/sig cli

[knight42]

/milestone v1.25

[k8s-ci-robot]

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

In response to this:

/milestone v1.25

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.

[Priyankasaggu11929]

/milestone v1.25

[Priyankasaggu11929]

Hello @knight42 👋, 1.25 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PST on Thursday June 16, 2022.

For note, This enhancement is targeting for stage alpha for 1.25 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP file using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable
• KEP has a updated detailed test plan section filled out
• KEP has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

Looks like for this one, we would need to get the open KEP PR #3289 merged by Enhancements Freeze:

For note, the status of this enhancement is marked as at risk. Thanks for keeping the issue description up-to-date!

[Priyankasaggu11929]

With KEP PR #3289 merged, this enhancement is ready for the upcoming enhancements freeze.

For note, the status is not marked as tracked in the enhancements tracking sheet. Thank you!

[knight42]

@Priyankasaggu11929 I think the following could be marked as done now:

• KEP file using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable
• KEP has a updated detailed test plan section filled out
• KEP has a production readiness review that has been completed and merged into k/enhancements.