Handle warnings/errors in Helm CLI client #6076
Conversation
kubermatic-bot
added
release-note
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: xrstf 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 |
kubermatic-bot
added
approved
|
/cherrypick release/v2.15 |
|
@xrstf: once the present PR merges, I will cherry-pick it on top of release/v2.15 in a new PR and assign it to you. 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. |
|
/lgtm |
|
LGTM label has been added. Git tree hash: a816ffb7b219e09e2894d09401194d9744b68c5d
|
|
@xrstf: new pull request created: #6083 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 this PR does / why we need it:
With v3.3.2, Helm started to check the file mode for the given kubeconfig (helm/helm#8748). If the kuebconfig is world-readable, it issues a warning on stderr. Before this PR, our Helm CLI Client just combined stdout and stderr for simplicity, but this won't work anymore.
This PR splits stdout and stderr again, fixing the version check.
Which issue(s) this PR fixes:
Fixes #6070
Does this PR introduce a user-facing change?: