community
community copied to clipboard
Document Security Self-Assessment.
/assign @rmohr
@rmohr How are you going with this? Should I reassign it to someone? @iholder101 might be able to take this on.
:+1: I'll gladly take this over if @rmohr wants to give it away
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@kubevirt-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten./close
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-sigs/prow repository.
I believe @jean-edouard has a draft of this assessment that is close to ready to be added.
The Security self-assessment has been completed and merged into the CNCF TAG-security repo. Thank you @jean-edouard !!