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 volume plugin label to SELinux metrics #121069
Conversation
Record volume plugin name when a volume in a Pod needs a different "mount -o context" value than the actually mounted one. We expect that NFS, CIFS and CephFS volumes would be able to mount such volumes just fine with multiple "-o context" values. We know that the block-volume based ones (ext4, xfs, btrfs, ...) cannot do that. Therefore want to distinguish the volume plugin in metrics, anything block-volume based could break an existing application.
c78d540
to
0be5fdb
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jsafrane 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 |
/sig storage |
/triage accepted |
/assign @xing-yang @msau42 |
/lgtm |
LGTM label has been added. Git tree hash: 9f6d1534e475bab8bbf5e31d3d4e1174fb0a99d8
|
What type of PR is this?
/kind feature
What this PR does / why we need it:
Record volume plugin name when a volume in a Pod needs a different
"mount -o context"
value than the actually mounted one.We expect that NFS, CIFS and CephFS volumes would be able to mount such volumes just fine with multiple
"-o context"
values.We know that the block-volume based ones (ext4, xfs, btrfs, ...) cannot do that.
Therefore I want to distinguish the volume plugin in metrics, anything block-volume based could break an existing application.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: