-
Notifications
You must be signed in to change notification settings - Fork 40.3k
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
Use docker logs
directly if the docker logging driver is not json-file
#42195
Use docker logs
directly if the docker logging driver is not json-file
#42195
Conversation
bee73c0
to
5ade58b
Compare
5ade58b
to
b948562
Compare
docker logs
directory if the docker logging driver is notdocker logs
directly if the docker logging driver is not json-file
95d801d
to
27ba4f2
Compare
3066671
to
31d0f66
Compare
I manually verified this PR by running node e2e ConfigMap test https://github.com/kubernetes/kubernetes/blob/master/test/e2e/common/configmap.go. The test relies on container log output.
|
31d0f66
to
7c01bf1
Compare
@yujuhong Removed the node status part. |
/lgtm Thanks! |
|
||
// IsCRISupportedLogDriver checks whether the logging driver used by docker is | ||
// suppoted by native CRI integration. | ||
func IsCRISupportedLogDriver(client dockertools.DockerInterface) (bool, error) { |
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.
nit: do we need to log the driver name? It could help for debugging if there is something wrong when getting logs.
@k8s-bot node e2e test this. |
@k8s-bot non-cri node e2e test this. |
7c01bf1
to
7c261bf
Compare
[APPROVALNOTIFIER] This PR is APPROVED The following people have approved this PR: Random-Liu, yujuhong Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
Rebased, assign lgtm again. |
@Random-Liu: The following test(s) failed:
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
@k8s-bot gce etcd3 e2e test this |
This is a bug fix to make CRI integration work with docker journald logging driver. |
Automatic merge from submit-queue (batch tested with PRs 41931, 39821, 41841, 42197, 42195) |
Fixes #41996.
Post the PR first, I still need to manually test this, because we don't have test coverage for journald logging pluggin.
@yujuhong @dchen1107
/cc @kubernetes/sig-node-pr-reviews