search

kubernetes-retired / cluster-api-provider-nested

Cluster API Provider for Nested Clusters
Apache License 2.0
301 stars 67 forks source link

Create a SECURITY_CONTACTS file. #237

Closed k8s-triage-robot closed 2 years ago

k8s-triage-robot commented 2 years ago

As per the email sent to kubernetes-dev[1], please create a SECURITY_CONTACTS file.

The template for the file can be found in the kubernetes-template repository[2]. A description for the file is in the steering-committee docs[3], you might need to search that page for "Security Contacts".

Please feel free to ping me on the PR when you make it, otherwise I will see when you close this issue. :)

Thanks so much, let me know if you have any questions.

(This issue was generated from a tool, apologies for any weirdness.)

[1] https://groups.google.com/forum/#!topic/kubernetes-dev/codeiIoQ6QE [2] https://github.com/kubernetes/kubernetes-template-project/blob/master/SECURITY_CONTACTS [3] https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance-template-short.md

justaugustus commented 2 years ago

This issue may have been opened in error due to a bug in the logic for discovering SECURITY_CONTACTS files. For more information, please see this notice to kubernetes-dev.

As this has [re]opened multiple issues across Kubernetes orgs, I will not attempt to answer comments on individual issues. Feel free to reply to the linked kubernetes-dev thread or file an issue here to continue the discussion. /close

k8s-ci-robot commented 2 years ago

@justaugustus: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/cluster-api-provider-nested/issues/237#issuecomment-989464054): >This issue may have been opened in error due to a bug in the logic for discovering SECURITY_CONTACTS files. >For more information, please see this notice to [kubernetes-dev](https://groups.google.com/g/kubernetes-dev/c/yFlPFIYJCt8). > >As this has [re]opened multiple issues across Kubernetes orgs, I will not attempt to answer comments on individual issues. >Feel free to reply to the linked kubernetes-dev thread or file an issue [here](https://github.com/justaugustus/secping/issues) to continue the discussion. >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.