Skip to content
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 Giant Swarm #118

Closed
stone-z opened this issue Dec 4, 2020 · 1 comment · Fixed by kubernetes/k8s.io#1820
Closed

private-distributors-list: add Giant Swarm #118

stone-z opened this issue Dec 4, 2020 · 1 comment · Fixed by kubernetes/k8s.io#1820

Comments

@stone-z
Copy link

stone-z commented Dec 4, 2020

Actively monitored security email alias for our project: security@giantswarm.io

1. Be an actively maintained and CNCF certified distribution of Kubernetes components.
Yes, we have active AWS, Azure, and on-prem distributions.
Sample AWS conformance report: cncf/k8s-conformance#1052

2. Have a user base not limited to your own organization.
Yes, some public customers are listed on our website

3. Have a publicly verifiable track record up to present day of fixing security issues.
We announce changes in our release notes. Two examples with security fixes: 1, 2.

4. Not be a downstream or rebuild of another distribution.
We are our own platform

5. Be a participant and active contributor in the community.
Some public events are listed on our website.
Some individual contributors and PRs from our organization:
https://github.com/njuettner
https://github.com/webwurst
kubernetes/kops#8780
kubernetes-sigs/cluster-api-provider-azure#978
kubernetes/kube-state-metrics#1238

6. Accept the Embargo Policy.
We accept

7. Be willing to contribute back.
Happily

8. Have someone already on the list vouch for the person requesting membership on behalf of your distribution.
Kinvolk has kindly agreed to vouch for us

@stone-z
Copy link
Author

stone-z commented Feb 25, 2021

Hi folks, just a nudge -- any way we can help here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant