-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Add datapolicy tags to pkg/kubelet/ #96004
Add datapolicy tags to pkg/kubelet/ #96004
Conversation
@serathius: GitHub didn't allow me to request PR reviews from the following users: PurelyApplied. Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs. 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. |
/assign @yujuhong |
/retest |
ping @yujuhong |
/milestone clear |
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.
/lgtm
As per #95997 I'm assuming the StaticPodURLHeader headers could potentially contain auth info.
/triage accepted |
/remove-lifecycle rotten |
@ehashman: Reopened this PR. 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. |
/assign @liggitt see #107121 (review) |
@@ -92,7 +92,7 @@ type KubeletConfiguration struct { | |||
// staticPodURL is the URL for accessing static pods to run | |||
StaticPodURL string |
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.
the URL can contain sensitive info as well as query parameters, right?
The description links to a KEP marked as deprecated. Is there an updated link or doc describing why we're adding these tags (for static analysis only, I assume) |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ehashman, liggitt, mrunalp, serathius 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 |
While the linked KEP is deprecated, these are still used by the stable KEP 1933. Let me see if someone can edit that into the docs release note. |
I updated the PR description to link to that KEP instead, thanks |
/hold cancel |
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
1 similar comment
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
Done |
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
2 similar comments
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
/kind feature
What this PR does / why we need it:
This PR adds "datapolicy" tags to golang structures as described in Defend against logging secrets via static analysis. Those tags will be used by for ensuring this data will not be written to logs by Kubernetes system components.
List of datapolicy tags available:
security-key
- for TLS certificate keys. Keywords:key
,cert
,pem
token
- for HTTP authorization tokens. Keywords:token
,secret
,header
,auth
password
- anything passwordlike. Keywords:password
Special notes for your reviewer:
Due to size of Kubernetes codebase first iteration of tagging was done based on greping for particular keyword. Please ensure that tagged fields do contain type of sensitive data that matches their tag. Feel free to suggest any additional places that you think should be tagged.
Does this PR introduce a user-facing change?:
No
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/cc @PurelyApplied
/sig instrumentation security
/priority important-soon
/milestone v1.20