Kubernetes Security Release Process and Security Committee documentation.
The Product Security Committee (PSC) is responsible for triaging and handling the security issues for Kubernetes. Following are the current Product Security Committee members:
- CJ Cullen (@cjcullen)
<[email protected]> - Joel Smith (@joelsmith)
<[email protected]> - Jordan Liggitt (@liggitt)
<[email protected]>[4096R/0x39928704103C7229] - Luke Hinds (@lukehinds)
[email protected] - Micah Hausler (@micahhausler)
<[email protected]> - Tim Allclair (@tallclair)
<[email protected]>
Associate members include:
- Craig Ingram (@cji)
<[email protected]> - Swamy Shivaganga Nagaraju (@swamymsft)
<[email protected]> - Mo Khan (@enj)
<[email protected]>
Emeritus members:
- Brandon Philips (@philips)
<[email protected]> - Jess Frazelle (@jessfraz)
<[email protected]> - Jonathan Pulsifer (@jonpulsifer)
<[email protected]>
There are a number of contact points for the PSC and release managers in charge of security releases. Please use the correct forum for the best and fastest response.
| List or Group | Visibility | Uses |
|---|---|---|
| [email protected] | Private | Kubernetes security disclosures. This list is closely monitored and triaged by the PSC. See the disclosure guide for full details. |
| kubernetes-security-discuss Google Group | Public | Discussion about security disclosure handling, this document, and other updates. |
| [email protected] | Private | Release Managers private discussion. All members are subscribed to [email protected]. |
| [email protected] | Private | PSC private discussion. All members are subscribed to [email protected] |
Learn how to engage with the Kubernetes community on the community page.
Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.