-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[PodSecurity] Update monitoring proposal #2990
Conversation
d51a1ef
to
c85d1e9
Compare
request can increment this metric 3 times, once for each mode. `audit` and `warn` mode metrics | ||
are only incremented for violations. If this admission controller is enabled, every | ||
evaluated request will at least increment the `enforce` total. |
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.
if someone wanted to figure out the proportion of allowed/denied audit or warn requests, they'd now have to compare the number of denied audit or warn requests to the total number of mode=enforce requests, right? that could be ok, but is non-obvious
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.
Yeah. We could have a separate metric for tracking total evaluations, but that seems unnecessary. I agree it's non-obvious, but maybe it's something we can just add to the playbook...
0c837c4
to
edb6e9a
Compare
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
/lgtm for instrumentation |
Co-authored-by: Jordan Liggitt <jordan@liggitt.net>
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt, tallclair 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 |
* [PodSecurity] Update monitoring proposal * fixup! [PodSecurity] Update monitoring proposal * Apply suggestions from code review Co-authored-by: Jordan Liggitt <jordan@liggitt.net> Co-authored-by: Jordan Liggitt <jordan@liggitt.net>
* [PodSecurity] Update monitoring proposal * fixup! [PodSecurity] Update monitoring proposal * Apply suggestions from code review Co-authored-by: Jordan Liggitt <jordan@liggitt.net> Co-authored-by: Jordan Liggitt <jordan@liggitt.net>
Update the PodSecurity KEP with some monitoring changes. These changes are motivated by corner cases encountered in the implementation: kubernetes/kubernetes#104217