遵循以下最佳实践的项目将能够自愿的自我认证,并显示他们已经实现了核心基础设施计划(OpenSSF)徽章。 显示详细资料
[](https://www.bestpractices.dev/projects/5368)
<a href="https://www.bestpractices.dev/projects/5368"><img src="https://www.bestpractices.dev/projects/5368/badge"></a>
The Kubernetes Security Profiles Operator (SPO) is an out-of-tree Kubernetes enhancement which aims to make it easier to use SELinux, seccomp and AppArmor in Kubernetes clusters.
The contributing page links back to the Kubernetes community contributing guide, which further explains the requirements for acceptable contributions:
https://github.com/kubernetes-sigs/security-profiles-operator/blob/master/CONTRIBUTING.md#getting-started https://github.com/kubernetes/community/blob/master/contributors/guide/contributing.md#best-practices
https://github.com/kubernetes-sigs/security-profiles-operator/issues
The test policy is documented and followed by contributors. There is no hard rule in terms of every PR must contain tests, however, the PR template also highlights the need of such practice.
https://github.com/kubernetes-sigs/security-profiles-operator/blob/main/CONTRIBUTING.md#contributing-steps https://github.com/kubernetes-sigs/security-profiles-operator/blob/main/.github/PULL_REQUEST_TEMPLATE.md
make verify would break a build and therefore would impede a change to be merged.
make verify
https://github.com/kubernetes-sigs/security-profiles-operator/blob/master/Makefile
警告:需要更长的理由。
https://github.com/kubernetes-sigs/security-profiles-operator/blob/master/Makefile#L286
The application is based in golang, and although there is an intention to add fuzzers to it, it hasn't been done yet. There is a small proportion (< 1%) of C code for a experimental ebpf implementation, which shall be fuzzed once it is stable.
后退