Skip to content
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

Log or expose standard error from internal exec #4254

Closed
shawkins opened this issue Jul 5, 2022 · 0 comments · Fixed by #4288
Closed

Log or expose standard error from internal exec #4254

shawkins opened this issue Jul 5, 2022 · 0 comments · Fixed by #4288
Assignees
Milestone

Comments

@shawkins
Copy link
Contributor

shawkins commented Jul 5, 2022

Is your enhancement related to a problem? Please describe

If you use pod file operations, such as copy, the stdErr is not requested / captured.

Describe the solution you'd like

We may not simply be able to use terminateOnError because a command like tar will report things on stdErr such as "stripping leading /" - although we may be able to workaround that in other ways like using -C.

At the very least it should be logged.

If a monitor like facility is added via #4236, the stdErr could be exposed there as well.

Describe alternatives you've considered

No response

Additional context

No response

@shawkins shawkins self-assigned this Jul 19, 2022
@shawkins shawkins added this to the 6.1.0 milestone Jul 19, 2022
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Jul 21, 2022
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Aug 1, 2022
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Aug 8, 2022
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Aug 8, 2022
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Aug 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant