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
Split stdout and stderr log stream of container #3288
Comments
/sig node |
/milestone v1.25 |
@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:
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. |
/milestone v1.25 |
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 Here's where this enhancement currently stands:
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 |
With KEP PR #3289 merged, this enhancement is ready for the upcoming enhancements freeze. For note, the status is not marked as |
@Priyankasaggu11929 I think the following could be marked as done now:
|
Hi @knight42, Enhancements team here again 👋 Checking in as we approach Code Freeze at 01:00 UTC on Wednesday, 3rd August 2022. Please ensure that the following items are completed before the code-freeze:
Currently, the status of the enhancement is marked as Thanks :) |
Hey @knight42 reaching out again as we approach Code Freeze at 01:00 UTC on this Wednesday i.e 3rd August 2022. |
@Atharva-Shinde Hi, I think we need to move it to next release v1.26. Thanks! |
Thanks for the update @knight42. /milestone clear |
/milestone v1.26 |
/stage alpha |
Hey @knight42 👋, 1.26 Enhancements team here! Just checking in as we approach Enhancements Freeze on 18:00 PDT on Thursday 6th October 2022. This enhancement is targeting for stage Here's where this enhancement currently stands:
For this KEP, we would need to:
The status of this enhancement is marked as |
/milestone v1.26 (this is a carry over from prior release) |
Hello @knight42 👋, just a quick check-in again, as we approach the 1.26 Enhancements freeze. Please plan to get the action items mentioned in my comment above done before Enhancements freeze on 18:00 PDT on Thursday 6th October 2022 i.e tomorrow For note, the current status of the enhancement is marked |
Hello 👋, 1.26 Enhancements Lead here. Unfortunately, this enhancement did not meet requirements for enhancements freeze. If you still wish to progress this enhancement in v1.26, please file an exception request. Thanks! /milestone clear |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale I am available now and will pick it up recently. |
@knight42 are you still available? Should we track this KEP for 1.28? |
Yes please, I think I could make it. |
/milestone v1.28 |
@knight42 can you please send update to kep.yaml to include this in 1.28? |
@knight42 can you please send update to kep.yaml to include this in 1.29? |
Hi @SergeyKanzhelev, I have filed #4221 to update milestones. |
Hi @knight42, is this targeting 1.29? If it is, can you please make sure the |
Yeah I hope so, thanks for reminding! /label lead-opted-in |
@knight42: Can not set label lead-opted-in: Must be member in one of these teams: [release-team-enhancements release-team-leads sig-api-machinery-leads sig-apps-leads sig-architecture-leads sig-auth-leads sig-autoscaling-leads sig-cli-leads sig-cloud-provider-leads sig-cluster-lifecycle-leads sig-contributor-experience-leads sig-docs-leads sig-instrumentation-leads sig-k8s-infra-leads sig-multicluster-leads sig-network-leads sig-node-leads sig-release-leads sig-scalability-leads sig-scheduling-leads sig-security-leads sig-storage-leads sig-testing-leads sig-windows-leads] In response to this:
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. |
Hi @knight42 👋, 1.29 Enhancements Lead here. Unfortunately, this enhancement did not meet requirements for v1.29 enhancements freeze. |
Enhancement Description
k/enhancements
) update PR(s): KEP 3288: Split stdout and stderr log stream #3289k/k
) update PR(s):Stream
to be set inPodLogOptions
kubernetes#110794k/website
) update PR(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: