kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

udpate content/zh/docs/concepts/configuration/overview.md

This commit is contained in:
helight 2020-12-03 16:49:23 +08:00
parent d1f92ec276
commit fff830aa51
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/zh/docs/concepts/configuration/overview.md
View File

@ -84,7 +84,7 @@ This is a living document. If you think of something that is not on this list bu
<!--
A Deployment, which both creates a ReplicaSet to ensure that the desired number of Pods is always available, and specifies a strategy to replace Pods (such as [RollingUpdate](/docs/concepts/workloads/controllers/deployment/#rolling-update-deployment)), is almost always preferable to creating Pods directly, except for some explicit [`restartPolicy: Never`](/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy) scenarios. A [Job](/docs/concepts/workloads/controllers/jobs-run-to-completion/) may also be appropriate.
-->
除了一些显式的[`restartPolicy: Never`](/zh/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy)场景外，Deployment 通常比直接创建 Pod 要好得多，它既可以创建一个 ReplicaSet 集来确保所需数量的 Pod 始终可用，也可以指定替换 Pod 的策略(例如 [RollingUpdate](/zh/docs/concepts/workloads/controllers/deployment/#rolling-update-deployment))。Job 也可能是更好的选择。
除了一些显式的[`restartPolicy: Never`](/zh/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy)场景外，Deployment 通常比直接创建 Pod 要好得多，它既可以创建一个 ReplicaSet 集来确保所需数量的 Pod 始终可用，也可以指定替换 Pod 的策略(例如 [RollingUpdate](/zh/docs/concepts/workloads/controllers/deployment/#rolling-update-deployment))。但是 Job 也可能是更好的选择。
<!--
## Services