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:
- Brandon Philips (@philips)
<bphilips@redhat.com>[4096R/154343260542DF34] - CJ Cullen (@cjcullen)
<cjcullen@google.com> - Tim Allclair (@tallclair)
<tallclair@google.com>[4096R/0x5E6F2E2DA760AF51] - Jordan Liggitt (@liggitt)
<jordan@liggitt.net>[4096R/0x39928704103C7229] - Joel Smith (@joelsmith)
<joelsmith@redhat.com> - Jonathan Pulsifer (@jonpulsifer)
<jonathan.pulsifer@shopify.com>
Associate members include:
- Micah Hausler (@micahhausler)
<mhausler@amazon.com> - Luke Hinds (@lukehinds)
lhinds@redhat.com - Swamy Shivaganga Nagaraju (@swamymsft)
<gaswamy@microsoft.com>
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 |
|---|---|---|
| security@kubernetes.io | 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. |
| security-release-team@kubernetes.io | Private | Release manager private discussion. All members are subscribed to security@kubernetes.io. |
| security-discuss-private@kubernetes.io | Private | PSC private discussion. All members are subscribed to security@kubernetes.io |
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.