-
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
clusterctl log output should be printed to stderr #2963
Comments
@wfernandes: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
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. |
The same should apply to cluster config provider -o yaml |
/milestone v0.3.x |
Easy one liner to intentionally break and create both debug and error log output (by using clusterctl without a provider): |
I just tested this on the current clusterctl cli and it seems to work.
It seems that this got fixed as part of PR #3124 /close |
@wfernandes: Closing this issue. In response to this:
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. |
What steps did you take and what happened:
When I print out higher verbosity logs from clusterctl for example
clusterctl config cluster -v5 test -i aws
, it prints out the logs and output to stdout. So piping the output such asclusterctl config cluster -v5 test -i aws | kubectl apply -f -
doesn't work.What did you expect to happen:
I'd expect the logs to be printed out to stderr which is a more ubiquitous behavior I believe.
/kind bug
/area clusterctl
/help
The text was updated successfully, but these errors were encountered: