-
Notifications
You must be signed in to change notification settings - Fork 2k
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
feat: Initialize OpenVEX feed #2275
Conversation
This issue is currently awaiting triage. If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the The 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. |
Welcome @shafeeqes! |
/lgtm Thanks for your contribution! |
/ok-to-test |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mrueg, shafeeqes 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 |
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.
Hello, @shafeeqes. Thank you for your work here!
I'm not quite sure though, what the json
template is for? IIUC openvexctl
can create manifests for us which can be stored in ./.openvex
and attested to KSM images (however, since KSM images are generated from k8s.io
, do we know if that respects (picks up) the manifests from here)?
What this PR does / why we need it:
Initialize OpenVEX feed.
#SecuritySlam
Which issue(s) this PR fixes :
Fixes part of #2274