convert to new dir structure

Author: deads2k

keps/sig-api-machinery/20190927-insecure-backend-proxy.md renamed to keps/sig-api-machinery/1295-insecure-backend-proxy/README.md

@@ -1,30 +1,4 @@
----
-title: Insecure Backend Proxy
-authors:
-  - "@deads2k"
-owning-sig: sig-api-machinery
-participating-sigs:
-  - sig-api-machinery
-  - sig-auth
-  - sig-cli
-reviewers:
-  - "@sttts"
-  - "@cheftako"
-  - "@liggitt"
-  - "@soltysh"
-approvers:
-  - "@lavalamp"
-  - "@mikedanese"
-editor: TBD
-creation-date: 2019-09-27
-last-updated: 2019-09-27
-status: implementable
-see-also:
-replaces:
-superseded-by:
----
-
-# Insecure Backend Proxy
+# KEP-1295: Insecure Backend Proxy
 
 When trying to get logs for a pod, it is possible for a kubelet to have an expired serving certificate.
 If a client chooses, it should be possible to bypass the default behavior of the kube-apiserver and allow the kube-apiserver

keps/sig-api-machinery/1295-insecure-backend-proxy/kep.yaml

@@ -0,0 +1,40 @@
+title: Insecure Backend Proxy
+kep-number: 1295
+authors:
+  - "@deads2k"
+owning-sig: sig-api-machinery
+participating-sigs:
+  - sig-api-machinery
+  - sig-auth
+  - sig-cli
+status: implemented
+creation-date: 2019-09-27
+reviewers:
+  - "@sttts"
+  - "@cheftako"
+  - "@liggitt"
+  - "@soltysh"
+approvers:
+  - "@lavalamp"
+  - "@mikedanese"
+see-also:
+
+# The target maturity stage in the current dev cycle for this KEP.
+stage: beta
+
+# The most recent milestone for which work toward delivery of this KEP has been
+# done. This can be the current (upcoming) milestone, if it is being actively
+# worked on.
+latest-milestone: "v1.17"
+
+# The milestone at which this feature was, or is targeted to be, at each stage.
+milestone:
+  beta: "v1.17"
+
+# The following PRR answers are required at alpha release
+# List the feature gate name and the components for which it must be enabled
+feature-gates:
+  - name: AllowInsecureBackendProxy
+    components:
+      - kube-apiserver
+disable-supported: true