added files to sig-security

[chetak123]

Signed-off-by: Ayushman [email protected]

issue #9

Created new directories and files in sig-security

[k8s-ci-robot]

Welcome @chetak123!

It looks like this is your first PR to kubernetes/sig-security 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/sig-security has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[PushkarJ]

/lgtm
/assign IanColdwater tabbysable
/cc @savitharaghunathan @reylejano
/hold for kubernetes/community#6176

[savitharaghunathan]

I feel like we should remove the hold from this PR. k/community issue is waiting on getting this PR merged.

Personally I would like the content to be available here, before we remove it from k/community. @PushkarJ @reylejano what do you all think?

[PushkarJ]

Maybe we can keep the /hold on both until we get /approve from Ian and Tabby? Once both the PRs are approved, we can unhold them together, thus avoiding two places having same content at the same time, even if it is for a short period.

[reylejano]

I agree we can wait till both PRs are approved and unhold together

[tabbysable]

/approve

[tabbysable]

I've asked for a few changes to make the new directories consistent with the ones from the old repo.

Once you've done that, you can avoid needing to manually squash your commits by using magic similar to what @PushkarJ did in kubernetes/community#6176

Thanks a lot, @chetak123!

[tabbysable]

@chetak123 can you please rename this directory to sig-security-docs to match the previous one under k/community?

It seems a little silly since this is now our sig-security repo, but I'm afraid that a "docs" subdirectory sounds like it's documentation about us or something, rather than the name of a subproject like it is.

[tabbysable]

@chetak123 Similarly, can you please rename this directory to sig-security-external-audit for consistency with the files' previous home in the k/community repo?

[tabbysable]

@chetak123 After renaming third party audit to sig-security-external-audit, can you please move these 3 files (owners, readme, and roadmap) up one level and remove the resulting empty directory?

[tabbysable]

@chetak123 As with the other two directories, please rename this one to sig-security-tooling for consistency with the old directory

[tabbysable]

/remove-approve

[PushkarJ]

@chetak123 thank you for the fixes in naming!!
/lgtm
@tabbysable ready for your review

[tabbysable]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chetak123, tabbysable

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:

• OWNERS [tabbysable]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[PushkarJ]

/unhold for kubernetes/community#6176 (comment)

[PushkarJ]

/hold cancel