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
Mask Ceph RBD adminSecrets in logs when logLevel >= 4 #95245
Conversation
Welcome @sfowl! |
Hi @sfowl. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
/lgtm |
/retest |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jsafrane, sfowl 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 |
/retest |
/priority important-soon |
…upstream-release-1.17 Automated cherry pick of #95245: Mask Ceph RBD adminSecrets in logs when logLevel >= 4
…upstream-release-1.19 Automated cherry pick of #95245: Mask Ceph RBD adminSecrets in logs when logLevel >= 4
…upstream-release-1.18 Automated cherry pick of #95245: Mask Ceph RBD adminSecrets in logs when logLevel >= 4
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
credentials/secrets should not be exposed in logs, even at high logging levels
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Considered removing "key <masked" entirely from log messages, but thought that made it unclear whether a key was used or not.
Does this PR introduce a user-facing change?: