New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
private-distributors-list: add Loodse #48
Comments
This looks fine. Approved. @swamymsft can you format this into a PR against https://github.com/kubernetes/security/blob/master/private-distributors-list.md |
Sure, I will get this done |
Fixed by #50 |
tallclair
added a commit
to tallclair/k8s.io
that referenced
this issue
Nov 15, 2019
Instantiate changes in kubernetes/committee-security-response#50 for kubernetes/committee-security-response#48. /cc @swamymsft @scheeles
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Actively monitored security email alias for our project: security@loodse.com
1. Be an actively maintained and CNCF certified distribution of Kubernetes components.
Yes, we have Kubermatic and KubeOne https://github.com/kubermatic/kubeone
2. Have a user base not limited to your own organization.
KubeOne is open source and kubermatic is used by several enterprises e.g. https://metakube.syseleven.de
3. Have a publicly verifiable track record up to present day of fixing security issues.
We are working on upstream patches for https://github.com/kubernetes/dashboard
Additional we have an security newsletter where we announce all upstream patches https://www.loodse.com/newsletter/
4. Not be a downstream or rebuild of another distribution.
This does not apply, Kubermatic and KubeOne are unique.
5. Be a participant and active contributor in the community.
We have several member who are working on upstream project e.g.
https://github.com/nikhita
https://github.com/maciaszczykm
https://github.com/floreks
https://github.com/alvaroaleman
6. Accept the Embargo Policy.
We accept it
7. Be willing to contribute back.
We are definitely willing to help!
8. Have someone already on the list vouch for the person requesting membership on behalf of your distribution.
Brandon Philips
The text was updated successfully, but these errors were encountered: