Add feeds directory with OWNERS file under tooling sub-project

[PushkarJ]

Related to kubernetes/enhancements#3203

1. We need a directory under which the JSON blob exists: k/sig-security/sig-security-tooling/feeds/official-cve-feed.json
2. Create an OWNERS file
   made of aliases.

• The OWNERS file can include SRC alias security-response-committee and
• A new alias for sig-security-tooling-leads

Note: sig-security-tooling-leads alias will allow manual modification and rotation for members. It will need to be added here: https://github.com/kubernetes/sig-security/blob/main/OWNERS_ALIASES. For now add @nehaLohia27 and @PushkarJ under this alias.

/help-wanted
/good-first-issue
/sig security

[k8s-ci-robot]

@PushkarJ:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

Related to kubernetes/enhancements#3203

1. We need a directory under which the JSON blob exists: k/sig-security/sig-security-tooling/feeds/official-cve-feed.json
2. Create an OWNERS file
   made of aliases.

• The OWNERS file can include SRC alias security-response-committee and
• A new alias for sig-security-tooling-leads

Note: sig-security-tooling-leads alias will allow manual modification and rotation for members. It will need to be added here: https://github.com/kubernetes/sig-security/blob/main/OWNERS_ALIASES. For now add @nehaLohia27 and @PushkarJ under this alias.

/help-wanted
/good-first-issue
/sig security

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.

[chetak123]

/assign @chetak123

[PushkarJ]

@chetak123 thanks for assigning this. Currently we are discussing an alternative plan which may not need work on this issue here. So please hold off work on this, until we have consensus on approach

[chetak123]

OK sure

[chetak123]

Hey @PushkarJ I went through issue 3295 which says we don't require any robot account or fork, And I just wanted to confirm if this issue is still needed or not ?
Thanks.

[PushkarJ]

@chetak123 Good catch. We do not need it for now. If things change in future I will re-open

/close

[k8s-ci-robot]

@PushkarJ: Closing this issue.

In response to this:

@chetak123 Good catch. We do not need it for now. If things change in future I will re-open

/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/test-infra repository.