-
Notifications
You must be signed in to change notification settings - Fork 1.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
✨ Collect additional logs with CAPD log collector #11083
✨ Collect additional logs with CAPD log collector #11083
Conversation
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.
What files are you thinking about to capture in addition?
Maybe it makes sense to hardcode them instead :-)
Signed-off-by: Alexandr Demicev <[email protected]>
9c63193
to
9b7acec
Compare
@chrischdi These are logs specific to K3S and RKE2 bootstrap providers. We would like them to be collected in our e2e suite that's using CAPD |
/lgtm |
LGTM label has been added. Git tree hash: bf4d306e97cef331e294ccf4a5b9c5ef3dc1b7a9
|
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.
/approve
Thanks for this imporvement!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chrischdi 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 this PR does / why we need it:
I want to be able to collect more system logs from CAPD clusters than currently offered. This PR introduces a change to the DockerLogCollector structure that allows specifing additional systems logs.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
/area testing