From 514dc717121e7efc2f88c45c1e3e9b8e4c987536 Mon Sep 17 00:00:00 2001 From: makocchi Date: Wed, 13 Jun 2018 08:14:30 +0900 Subject: [PATCH] wrap contents by capture tags (#9036) --- content/en/docs/reference/issues-security/security.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/content/en/docs/reference/issues-security/security.md b/content/en/docs/reference/issues-security/security.md index 4c6c383f41..9613a6bc7c 100644 --- a/content/en/docs/reference/issues-security/security.md +++ b/content/en/docs/reference/issues-security/security.md @@ -1,5 +1,4 @@ --- - title: Kubernetes Security and Disclosure Information aliases: [/security/] reviewers: @@ -7,9 +6,15 @@ reviewers: - erictune - philips - jessfraz +content_template: templates/concept weight: 20 --- +{{% capture overview %}} +This page describes Kubernetes security and disclosure information. +{{% /capture %}} + +{{% capture body %}} ## Security Announcements Join the [kubernetes-announce](https://groups.google.com/forum/#!forum/kubernetes-announce) group for emails about security and major API announcements. @@ -45,3 +50,4 @@ As the security issue moves from triage, to identified fix, to release planning ## Public Disclosure Timing A public disclosure date is negotiated by the Kubernetes product security team and the bug submitter. We prefer to fully disclose the bug as soon as possible once a user mitigation is available. It is reasonable to delay disclosure when the bug or the fix is not yet fully understood, the solution is not well-tested, or for vendor coordination. The timeframe for disclosure is from immediate (especially if it's already publicly known) to a few weeks. As a basic default, we expect report date to disclosure date to be on the order of 7 days. The Kubernetes product security team holds the final say when setting a disclosure date. +{{% /capture %}}