-
Notifications
You must be signed in to change notification settings - Fork 39
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
Copy static pod logs to systemd via --send-static-pod-logs-to-systemd #11
Copy static pod logs to systemd via --send-static-pod-logs-to-systemd #11
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sttts 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 |
6b110cf
to
1cc910c
Compare
@smarterclayton @wking which do you prefer: sending static pods logs to systemd with |
1cc910c
to
abcf9b1
Compare
if len(name) == 0 { | ||
continue | ||
} | ||
podName, _, _ := unstructured.NestedString(container, "labels", "io.kubernetes.pod.name") |
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.
same here
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.
no, this can be missing (for non-pod containers). Emptyness check is what we want.
4f9859f
to
5d6231f
Compare
/retest |
5d6231f
to
ab5e0c1
Compare
/retest |
I haven't read the diff here, but it's green (if that's what you were waiting for), and I want the functionality it's advertising ;). |
Through da6d45b (Merge pull request openshift#890 from staebler/asset_loading_tests, 2019-02-04). Background for the networking.type validation entry is in this thread [1]. Forwarding static-pod longs to systemd is still in flight with [2]. [1]: openshift#1013 (comment) [2]: openshift/cluster-bootstrap#11
Through da6d45b (Merge pull request openshift#890 from staebler/asset_loading_tests, 2019-02-04). Background for the networking.type validation entry is in this thread [1]. The OpenStack HAProxy entry has wording based on [2] and Russell's out-of-band suggestions. Forwarding static-pod longs to systemd is still in flight with [3]. [1]: openshift#1013 (comment) [2]: https://github.com/openshift/installer/pull/1185/files#r253714521 [3]: openshift/cluster-bootstrap#11
Through da6d45b (Merge pull request openshift#890 from staebler/asset_loading_tests, 2019-02-04). Background for the networking.type validation entry is in this thread [1]. The OpenStack HAProxy entry has wording based on [2] and Russell's out-of-band suggestions. Forwarding static-pod longs to systemd is still in flight with [3]. [1]: openshift#1013 (comment) [2]: https://github.com/openshift/installer/pull/1185/files#r253714521 [3]: openshift/cluster-bootstrap#11
Through da6d45b (Merge pull request openshift#890 from staebler/asset_loading_tests, 2019-02-04). Background for the networking.type validation entry is in this thread [1]. The OpenStack HAProxy entry has wording based on [2] and Russell's out-of-band suggestions. Forwarding static-pod longs to systemd is still in flight with [3]. [1]: openshift#1013 (comment) [2]: https://github.com/openshift/installer/pull/1185/files#r253714521 [3]: openshift/cluster-bootstrap#11
Also in this space: containers/podman#2265. Presumably any changes to |
/hold |
We want to get static pod logs when the installer fails for some reason. We already scrape bootkube, cri-o and kubelet. This change will "copy" the cri-o container logs to systemd unit via
systemd-run --unit <pod-name> crictl logs <container-id>
. After that we can scrape it from the CI job through journald.Follow-up of openshift/release#2633.