diff options
| author | Brandon Philips <brandon.philips@coreos.com> | 2016-12-01 11:17:35 -0800 |
|---|---|---|
| committer | Brandon Philips <brandon.philips@coreos.com> | 2017-01-29 10:06:01 -0800 |
| commit | 723185b3e6ee790e34b246a036bbfe3987db06a4 (patch) | |
| tree | f4ef0a90527aa53e60c9511fe5d7dba5b4c2403f /vendor/github.com | |
| parent | 746b8a9ac6a73d111a43a57b53cba674da18440d (diff) | |
docs: devel: add security release process
After the v1.4.3 release I know we are all thinking about the security
disclosure and response plan for Kubernetes. I think we need to document some
internal processes, external communication templates/process, and improve the
disclosure systems.
This document is based on discussion and a Google doc on SIG Auth:
https://groups.google.com/forum/#!topic/kubernetes-sig-auth/Xq2f8bWCNDM
**Known issues**
- We haven't specified a way to cycle the Product Security Team; but we need
this process deployed quickly as our current process isn't working. I will put
a deadline of March 1st 2017 to sort that.
Tracking issue: https://github.com/kubernetes/kubernetes/issues/35462
Diffstat (limited to 'vendor/github.com')
0 files changed, 0 insertions, 0 deletions