Skip to content

Commit 0d86302

Browse files
k8s-ci-robotk8s-ci-robot
authored
Merge pull request #42063 from wilsonwu/trans-blog-23-2
[zh] Sync Updates to the Auto-refreshing Official CVE Feed blog into Chinese
2 parents 1e9c52a + f7a1455 commit 0d86302

File tree

1 file changed

+134
-0
lines changed
  • content/zh-cn/blog/_posts/2023-04-25-Updates-to-the-Auto-refreshing-Official-CVE-Feed

1 file changed

+134
-0
lines changed

‎content/zh-cn/blog/_posts/2023-04-25-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md

Lines changed: 134 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,134 @@
1+
---
2+
layout: blog
3+
title: 官方自动刷新 CVE 订阅源的更新
4+
date: 2023-04-25
5+
slug: k8s-cve-feed-beta
6+
---
7+
8+
<!--
9+
layout: blog
10+
title: Updates to the Auto-refreshing Official CVE Feed
11+
date: 2023-04-25
12+
slug: k8s-cve-feed-beta
13+
-->
14+
15+
**作者**：Cailyn Edwards (Shopify), Mahé Tardy (Isovalent), Pushkar Joglekar
16+
<!--
17+
**Authors**: Cailyn Edwards (Shopify), Mahé Tardy (Isovalent), Pushkar Joglekar
18+
-->
19+
20+
**译者**：Wilson Wu (DaoCloud)
21+
22+
<!--
23+
Since launching the [Auto-refreshing Official CVE feed](/docs/reference/issues-security/official-cve-feed/) as an alpha
24+
feature in the 1.25 release, we have made significant improvements and updates. We are excited to announce the release of the
25+
beta version of the feed. This blog post will outline the feedback received, the changes made, and talk about how you can help
26+
as we prepare to make this a stable feature in a future Kubernetes Release.
27+
-->
28+
自从在 1.25 版本中将[官方自动刷新 CVE 订阅源](/zh-cn/docs/reference/issues-security/official-cve-feed/)作为 Alpha
29+
功能启用以来，我们已经做了一些重大改进和更新。我们很高兴宣布该订阅源的 Beta 版现已发布。这篇博文将列举收到的反馈、所做的更改，
30+
还讨论了在未来 Kubernetes 版本中准备使其进阶成为一个稳定功能时你可以如何提供帮助。
31+
32+
<!--
33+
## Feedback from end-users
34+
-->
35+
## 来自最终用户的反馈 {#feadback-from-end-users}
36+
37+
<!--
38+
SIG Security received some feedback from end-users:
39+
- The JSON CVE Feed [did not comply](https://github.com/kubernetes/website/issues/36808)
40+
with the [JSON Feed specification](https://www.jsonfeed.org/) as its name would suggest.
41+
- The feed could also [support RSS](https://github.com/kubernetes/sig-security/issues/77)
42+
in addition to JSON Feed format.
43+
- Some metadata could be [added](https://github.com/kubernetes/sig-security/issues/72) to indicate the freshness of
44+
the feed overall, or [specific CVEs](https://github.com/kubernetes/sig-security/issues/63). Another suggestion was
45+
to [indicate](https://github.com/kubernetes/sig-security/issues/71) which Prow job recently updated the feed. See
46+
more ideas directly on the [the umbrella issue](https://github.com/kubernetes/sig-security/issues/1).
47+
- The feed Markdown table on the website [should be ordered](https://github.com/kubernetes/sig-security/issues/73)
48+
from the most recent to the least recently announced CVE.
49+
-->
50+
SIG Security 收到了一些最终用户的反馈：
51+
52+
- JSON CVE Feed 的名称与在 [JSON Feed 规范](https://www.jsonfeed.org/)中所建议的[不符](https://github.com/kubernetes/website/issues/36808)。
53+
- 除了 JSON Feed 格式之外，订阅源还可以[支持 RSS](https://github.com/kubernetes/sig-security/issues/77) 格式。
54+
- 可以[添加](https://github.com/kubernetes/sig-security/issues/72)一些元数据来表示整体订阅的实时性，
55+
或者[特殊 CVE](https://github.com/kubernetes/sig-security/issues/63) 内容。
56+
另一个建议是希望[指出](https://github.com/kubernetes/sig-security/issues/71)哪个 Prow 作业最近对订阅源进行了更新。
57+
可以直接在[问题汇总](https://github.com/kubernetes/sig-security/issues/1)中查看更多想法。
58+
- 网站上的订阅源 Markdown 表应按照 CVE 发布的时间顺序由近到远[排列](https://github.com/kubernetes/sig-security/issues/73)。
59+
60+
<!--
61+
## Summary of changes
62+
-->
63+
## 变更摘要 {#summary-of-changes}
64+
65+
<!--
66+
In response, the SIG did a [rework of the script generating the JSON feed](https://github.com/kubernetes/sig-security/pull/76)
67+
to comply with the JSON Feed specification from generation and add a
68+
`last_updated` root field to indicate overall freshness. This redesign needed a
69+
[corresponding fix on the Kubernetes website side](https://github.com/kubernetes/website/pull/38579)
70+
for the CVE feed page to continue to work with the new format.
71+
-->
72+
在回应中，SIG 对[生成 JSON 格式订阅源的脚本进行了修改](https://github.com/kubernetes/sig-security/pull/76)，
73+
让生成的内容符合 JSON Feed 规范，并添加 `last_updated` 根字段表示整体实时性。此重新设计需要
74+
[Kubernetes 网站的相应修复](https://github.com/kubernetes/website/pull/38579)，以便 CVE 订阅源页面基于新格式继续工作。
75+
76+
<!--
77+
After that, [RSS feed support](https://github.com/kubernetes/website/pull/39513)
78+
could be added transparently so that end-users can consume the feed in their
79+
preferred format.
80+
-->
81+
之后，完全透明的添加了 [RSS 订阅源支持](https://github.com/kubernetes/website/pull/39513)，以便最终用户使用订阅源时可以将其作为首选格式。
82+
83+
<!--
84+
Overall, the redesign based on the JSON Feed specification, which this time broke
85+
backward compatibility, will allow updates in the future to address the rest of
86+
the issue while being more transparent and less disruptive to end-users.
87+
-->
88+
总而言之，基于 JSON Feed 规范的重新设计（打破了向后兼容性）将允许后续进行更新以解决其余问题，同时令其更加透明且对最终用户的干扰做到较小。
89+
90+
<!--
91+
### Updates
92+
-->
93+
### 更新 {#updates}
94+
95+
<!--
96+
| **Title** | **Issue** | **Status** |
97+
| ------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
98+
| CVE Feed: JSON feed should pass jsonfeed spec validator | [kubernetes/webite#36808](https://github.com/kubernetes/website/issues/36808) | closed, addressed by [kubernetes/sig-security#76](https://github.com/kubernetes/sig-security/pull/76) |
99+
| CVE Feed: Add lastUpdatedAt as a metadata field | [kubernetes/sig-security#72](https://github.com/kubernetes/sig-security/issues/72) | closed, addressed by [kubernetes/sig-security#76](https://github.com/kubernetes/sig-security/pull/76) |
100+
| Support RSS feeds by generating data in Atom format | [kubernetes/sig-security#77](https://github.com/kubernetes/sig-security/issues/77) | closed, addressed by [kubernetes/website#39513](https://github.com/kubernetes/website/pull/39513)|
101+
| CVE Feed: Sort Markdown Table from most recent to least recently announced CVE | [kubernetes/sig-security#73](https://github.com/kubernetes/sig-security/issues/73) | closed, addressed by [kubernetes/sig-security#76](https://github.com/kubernetes/sig-security/pull/76) |
102+
| CVE Feed: Include a timestamp field for each CVE indicating when it was last updated | [kubernetes/sig-security#63](https://github.com/kubernetes/sig-security/issues/63) | closed, addressed by [kubernetes/sig-security#76](https://github.com/kubernetes/sig-security/pull/76) |
103+
| CVE Feed: Add Prow job link as a metadata field | [kubernetes/sig-security#71](https://github.com/kubernetes/sig-security/issues/71) | closed, addressed by [kubernetes/sig-security#83](https://github.com/kubernetes/sig-security/pull/83) |
104+
-->
105+
| **标题** | **Issue** | **状态** |
106+
| ------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
107+
| CVE Feed: JSON feed should pass jsonfeed spec validator | [kubernetes/webite#36808](https://github.com/kubernetes/website/issues/36808) | 已关闭，详见：[kubernetes/sig-security#76](https://github.com/kubernetes/sig-security/pull/76) |
108+
| CVE Feed: Add lastUpdatedAt as a metadata field | [kubernetes/sig-security#72](https://github.com/kubernetes/sig-security/issues/72) | 已关闭，详见：[kubernetes/sig-security#76](https://github.com/kubernetes/sig-security/pull/76) |
109+
| Support RSS feeds by generating data in Atom format | [kubernetes/sig-security#77](https://github.com/kubernetes/sig-security/issues/77) | 已关闭，详见：[kubernetes/website#39513](https://github.com/kubernetes/website/pull/39513)|
110+
| CVE Feed: Sort Markdown Table from most recent to least recently announced CVE | [kubernetes/sig-security#73](https://github.com/kubernetes/sig-security/issues/73) | 已关闭，详见：[kubernetes/sig-security#76](https://github.com/kubernetes/sig-security/pull/76) |
111+
| CVE Feed: Include a timestamp field for each CVE indicating when it was last updated | [kubernetes/sig-security#63](https://github.com/kubernetes/sig-security/issues/63) | 已关闭，详见：[kubernetes/sig-security#76](https://github.com/kubernetes/sig-security/pull/76) |
112+
| CVE Feed: Add Prow job link as a metadata field | [kubernetes/sig-security#71](https://github.com/kubernetes/sig-security/issues/71) | 已关闭，详见：[kubernetes/sig-security#83](https://github.com/kubernetes/sig-security/pull/83) |
113+
114+
<!--
115+
## What's next?
116+
-->
117+
## 接下来要做什么？ {#whats-next}
118+
119+
<!--
120+
In preparation to [graduate](https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/#feature-stages) the feed
121+
to stable i.e. `General Availability` stage, SIG Security is still gathering feedback from end users who are using the updated beta feed.
122+
-->
123+
为了此订阅源[进阶至](https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/#feature-stages)稳定阶段做准备，
124+
即 `General Availability` 阶段，SIG Security 仍将从最终用户持续收集他们使用最新 Beta 版订阅源后的反馈。
125+
126+
<!--
127+
To help us continue to improve the feed in future Kubernetes Releases please share feedback by adding a comment to
128+
this [tracking issue](https://github.com/kubernetes/sig-security/issues/1) or
129+
let us know on [#sig-security-tooling](https://kubernetes.slack.com/archives/C01CUSVMHPY)
130+
Kubernetes Slack channel, join [Kubernetes Slack here](https://slack.k8s.io).
131+
-->
132+
为了帮助我们在未来的 Kubernetes 版本中继续改进订阅源，请通过对此[跟踪 Issue](https://github.com/kubernetes/sig-security/issues/1)
133+
添加评论来分享反馈，或者通过 [#sig-security-tooling](https://kubernetes.slack.com/archives/C01CUSVMHPY)
134+
Kubernetes Slack 频道让我们获得更多信息，由此加入 [Kubernetes Slack](https://slack.k8s.io)。

0 commit comments

Comments
 (0)