@@ -99,6 +99,7 @@ tags, and then generate with `hack/update-toc.sh`.
99
99
- [ Test Plan] ( #test-plan )
100
100
- [ Graduation Criteria] ( #graduation-criteria )
101
101
- [ Alpha] ( #alpha )
102
+ - [ Beta] ( #beta )
102
103
- [ Upgrade / Downgrade Strategy] ( #upgrade--downgrade-strategy )
103
104
- [ Version Skew Strategy] ( #version-skew-strategy )
104
105
- [ Production Readiness Review Questionnaire] ( #production-readiness-review-questionnaire )
@@ -249,6 +250,8 @@ provide it to users of my platform.
249
250
Google Cloud Bucket)
250
251
- Using Hugo and other tooling (such as Netlify), publish the list from this
251
252
JSON blob on official k8s website during ` k/website ` build
253
+ - Generate an RSS feed (atom format) with hugo templates using the generated
254
+ JSON blob
252
255
253
256
### Risks and Mitigations
254
257
@@ -305,6 +308,8 @@ The steps to implement this design will involve a prow job that:
305
308
306
309
- A GCS bucket needs to be created. Example PR for this looks
307
310
like [ this] ( https://github.com/kubernetes/k8s.io/pull/2570/files )
311
+ - Additional custom fields need to be added to make JSON feed compliant with
312
+ https://validator.jsonfeed.org/
308
313
309
314
### Test Plan
310
315
@@ -326,7 +331,15 @@ This is a process KEP implemented using periodic prow job. This KEP is not imple
326
331
327
332
#### Alpha
328
333
329
- - KEP implementation is still in alpha and will be moved to beta based on community feedback within the next couple of release cycles.
334
+ - Feature implemented with working JSON feed and tabular list
335
+ - Initial e2e testing completed and alerting setup for detecting failures
336
+
337
+ #### Beta
338
+
339
+ - Gather feedback from developers and end users
340
+ - Make JSON feed compliant with ` jsonfeed ` spec
341
+ - Add ` RSS ` feed for the CVE list
342
+ - Add fields that signal freshness of the data
330
343
331
344
<!--
332
345
**Note:** *Not required until targeted at a release.*
0 commit comments