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

Add Ubuntu Security to security list for Kubernetes. #29

Closed
joemcmanus opened this issue May 6, 2019 · 3 comments · Fixed by #32
Closed

Add Ubuntu Security to security list for Kubernetes. #29

joemcmanus opened this issue May 6, 2019 · 3 comments · Fixed by #32

Comments

@joemcmanus
Copy link

Actively monitored security email alias for our project:
security@ubuntu.com

1. Be an actively maintained and CNCF certified distribution of Kubernetes components.
Canonical distributes and supports CNCF Kubernetes systems.

2. Have a user base not limited to your own organization.
Yes

3. Have a publicly verifiable track record up to present day of fixing security issues.
Please view usn.ubuntu.com to see the list of issues we have fixed over time.

4. Not be a downstream or rebuild of another distribution.
We are not.

5. Be a participant and active contributor in the community.
We are an active participant to the k8s community.

6. Accept the Embargo Policy.

Yes, the security team is aware of and participates in embargoed security issues.

7. Be willing to contribute back.

As a proud member of the Open Source community we would be happy to commit back.

8. Have someone already on the list vouch for the person requesting membership on behalf of your distribution.
Jorge Castro should be able to vouch for us.

Please let me know if you have any questions! -Joe

@philips
Copy link
Contributor

philips commented Jun 13, 2019

gah, sorry for not responding to this for weeks!

This looks good to me. So, I will add you to the list.

cc @castrojo

philips pushed a commit to philips/security that referenced this issue Jun 13, 2019
<!--
Please answer the following questions and provide supporting evidence for
meeting the membership criteria.
-->

**Actively monitored security email alias for our project:**
security@ubuntu.com

**1. Be an actively maintained and CNCF certified distribution of Kubernetes components.**
Canonical distributes and supports CNCF Kubernetes systems.

**2. Have a user base not limited to your own organization.**
Yes

**3. Have a publicly verifiable track record up to present day of fixing security issues.**
Please view usn.ubuntu.com to see the list of issues we have fixed over time.

**4. Not be a downstream or rebuild of another distribution.**
We are not.

**5. Be a participant and active contributor in the community.**
We are an active participant to the k8s community.

**6. Accept the Embargo Policy.**
<!-- https://github.com/kubernetes/security/blob/master/private-distributors-list.md#embargo-policy -->
Yes, the security team is aware of and participates in embargoed security issues.

**7. Be willing to contribute back.**
<!-- Per https://github.com/kubernetes/security/blob/master/private-distributors-list.md#contributing-back -->
As a proud member of the Open Source community we would be happy to commit back.

**8. Have someone already on the list vouch for the person requesting membership on behalf of your distribution.**
Jorge Castro should be able to vouch for us.

Please let me know if you have any questions! -Joe

Fixes kubernetes#29
@philips
Copy link
Contributor

philips commented Jun 13, 2019

PR is up, and an invite to the group was sent.

#32

/close

@k8s-ci-robot
Copy link
Contributor

@philips: Closing this issue.

In response to this:

PR is up, and an invite to the group was sent.

#32

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

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.

3 participants