-
Notifications
You must be signed in to change notification settings - Fork 460
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
feat: retrieve specific log stream of a container #1724
Conversation
6f2b8be
to
efe2ec7
Compare
@knight42 could you fix the lint errors? |
Signed-off-by: Jian Zeng <anonymousknight96@gmail.com>
123dbbd
to
7d81898
Compare
Sure! Please take another look. |
@feiskyer The test failure appears to be irrelevant. Could you please rerun the test? It seems I am unable to do so on my end. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks addressing the lint issues
Rerun works now
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: feiskyer, knight42 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Per kubernetes/kubernetes#127360 (comment), I am going to make crictl be able to fetch a specific log stream of a container.
BTW it turns out that crictl reads the log file directly (without any communication with apiserver or kubelet), so this change actually doesn't depend on k8s 1.32 APIs.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
Does this PR introduce a user-facing change?