Haser0305 commented on code in PR #370: URL: https://github.com/apache/yunikorn-site/pull/370#discussion_r1405350306
########## i18n/zh-cn/docusaurus-plugin-content-pages/release-announce/1.4.0.md: ########## @@ -33,77 +33,65 @@ Apache YuniKorn社区在此版本中修复了270个[JIRAs](https://issues.apache 发布日期: 2023-11-20 -## Incompatible changes +## 不兼容变更 -### Kubernetes version support -Running on Kubernetes 1.23 or earlier is **not** supported, for earlier Kubernetes releases use YuniKorn 1.3.0. +### Kubernetes 版本支援 +**不**支援在 Kubernetes 1.23 或更早期的版本中运行，对于早期的 Kubernetes 版本请使用 YuniKorn 1.3.0。 -**NOTE**: YuniKorn 1.3.0 is the last release that supports Kubernetes 1.23 or earlier. +**备注**: YuniKorn 1.3.0 是支援 Kubernetes 1.23 或更早期版本的最后一个版本。 -## Highlights +## 亮点 -### Kubernetes version support -YuniKorn 1.4.0 supports running on Kubernetes clusters from version 1.24 through to 1.28. +### Kubernetes 版本支援 +YuniKorn 1.4.0 支援在版本 1.24 到 1.28 的 Kubernetes 丛集上运行。 -Please see [YUNIKORN-1841](https://issues.apache.org/jira/browse/YUNIKORN-1841) for details. +详细资讯请参阅 [YUNIKORN-1841](https://issues.apache.org/jira/browse/YUNIKORN-1841) -### PreEnqueue plugin implementation -YuniKorn has added the pre-enqueue scheduling hook for the scheduler plugin. -This allows gating Pods that are not yet ready for scheduling due to queue pressure. -The pre-enqueue scheduling hook was added to Kubernetes via [KEP-3521](https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/3521-pod-scheduling-readiness/README.md). -It was turned on by default in Kubernetes 1.27. +### PreEnqueue 插件实作 +YuniKorn 添加了调度器插件的 pre-enqueue 调度挂钩。这允许根据队列压力阻止尚未就绪的 Pod 进行门控。Pre-enqueue 调度挂钩是通过 +[KEP-3521](https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/3521-pod-scheduling-readiness/README.md) 添加到 Kubernetes 中的。 他将在 Kubernetes 1.27 版本中默认开启。 -The feature allows managing quotas outside the Kubernetes Resource Quota system with a lower impact on the API server and default scheduler. -This functionality is important for the plugin implementation of YuniKorn only. -In the standard mode YuniKorn has always been gating pods without an external impact. +这功能允许在 Kubernetes 资源配额系统之外管理配额，并对于 API 伺服器和预设调度程序的影响较小。此功能仅对于 YuniKorn 的插件实作很重要。 +在标准模式下，YuniKorn 始终在没有外部影响的情况下对 Pod 进行门控。 -Please see [YUNIKORN-1844](https://issues.apache.org/jira/browse/YUNIKORN-1844) for details. +详细资讯请参阅 [YUNIKORN-1844](https://issues.apache.org/jira/browse/YUNIKORN-1844) -### Scoped logging -Logging within the YuniKorn code is now scoped to parts of the code base. -Scoped logging allows changing the logging level for a part of the code. -This gives administrators more control over the levels per subsystem. +### 范围化日志 +YuniKorn 程式码内的日志纪录建在仅限于部分程式码库。范围日志允许更改部分程式码的日志纪录等级。这使管理员可以更好地控制每个子系统的层级。 -Log levels can now also be specified in a textual form and not just as a number. -Documentation is part of the [service configuration](https://yunikorn.apache.org/docs/user_guide/service_config) +现在还可以以文字形式指定日志级别，而不仅仅是数字。文件是 [服务配置](https://yunikorn.apache.org/docs/user_guide/service_config) 的一部分。 -Please see [YUNIKORN-1823](https://issues.apache.org/jira/browse/YUNIKORN-1823) for details. +详细资讯请参阅 [YUNIKORN-1823](https://issues.apache.org/jira/browse/YUNIKORN-1823) -### Removal of the Spark Operator Application Manager -The Spark operator application manager was added to support the Spark operator as an external integration. -It added a full lifecycle for the Spark applications submitted via the operator. -The application manager was never turned on by default and needed a custom configuration to enable it. +### 移除 Spark Operator 应用程式管理器 +新增了 Spark operator 应用程式管理器以支援 Spark operator 作为外部整合。它为透过 operator 提交的 Spark 应用程式添加了完整的生命周期。 +应用程式管理器从未默认启用，需要自订配置才能启用。 -The implementation caused duplicate Spark applications to be created and was partially rolled back in [YUNIKORN-643](https://issues.apache.org/jira/browse/YUNIKORN-643) as part of YuniKorn 0.11. -The functionality that was left was also covered by the basic pod handling. -To reduce code maintenance the remaining code is now also removed without the loss of functionality. +此实作导致创建重复的 Spark application，并在作为 YuniKorn 0.11 的 [YUNIKORN-643](https://issues.apache.org/jira/browse/YUNIKORN-643) +中回滚。基本的 Pod 处理涵盖了剩下的功能。为了减少程式码维护，现在也删除了剩余的程式码，而不会失去功能。 -Please see [YUNIKORN-2092](https://issues.apache.org/jira/browse/YUNIKORN-2092) for details. +详细资讯请参阅 [YUNIKORN-2092](https://issues.apache.org/jira/browse/YUNIKORN-2092) -### Removal of the YuniKorn application CRD -YuniKorn 1.4.0 has removed the application CRD. -The application CRD was added to allow a simpler integration of applications with YuniKorn. -This integration never got used and all current integrations rely on simple labels or annotations on the pods. +### 移除 YuniKorn 应用程式 CRD +YuniKorn 1.4.0 已移除应用程式 CRD。添加应用程式 CRD 是为了更简单地将应用程式与 YuniKorn 整合。这种整合从未被使用过，目前所有整合都依赖 +Pod 上的简单标签或是注释。 -Please see [YUNIKORN-1672](https://issues.apache.org/jira/browse/YUNIKORN-1672) for details. +详细资讯请参阅 [YUNIKORN-1672](https://issues.apache.org/jira/browse/YUNIKORN-1672) -### Application traceability -Tracking and troubleshooting applications is specific for YuniKorn. -Kubernetes does not have an application concept. -An event system has been added to expose the changes to applications, queues and nodes for external consumption. +### 应用程式可追溯性 +追踪和故障排除应用程式是专门针对 YuniKorn。 Kubernetes 中没有应用程式的概念。新增了事件系统来公开应用程式、队列和节点的变更以公外部使用。 -Please see [YUNIKORN-1628](https://issues.apache.org/jira/browse/YUNIKORN-1628) +详细资讯请参阅 [YUNIKORN-1628](https://issues.apache.org/jira/browse/YUNIKORN-1628) -### Build updates -The YuniKorn builds no longer relies on centrally installed tools while building the binaries or images. -Each build will download and maintain its own set of tools, not even shared between checked out repositories. +### 建置更新 +在建置二进位档案或映像时，YuniKorn 建置不再依赖集中安装的工具。每个版本都会下载并维护自己的工具集，甚至不会在签出的除从库之间共用。 -The change was announced on the dev@ mailing list in late July. +这项变更于 7 月底在 dev@ 邮件单上宣布。 -Please see these jiras for details: +请参阅这些 jiras 已了解详细资讯: - k8shim: [YUNIKORN-1862](https://issues.apache.org/jira/browse/YUNIKORN-1862) and [YUNIKORN-1865](https://issues.apache.org/jira/browse/YUNIKORN-1865) - core: [YUNIKORN-1868](https://issues.apache.org/jira/browse/YUNIKORN-1868) - web UI: [YUNIKORN-1873](https://issues.apache.org/jira/browse/YUNIKORN-1873) ## Community Review Comment: Thank you for reminding, i have corrected it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
