@@ -208,7 +208,9 @@ Provisioner.
208
208
它可以使用 PersistentVolume 制备程序所准备的
209
209
[PersistentVolumes](/zh-cn/docs/concepts/storage/persistent-volumes/) 来提供稳定的存储。
210
210
211
- <!-- # ## Minimum ready seconds -->
211
+ <!--
212
+ # ## Minimum ready seconds
213
+ -->
212
214
# ## 最短就绪秒数 {#minimum-ready-seconds}
213
215
214
216
{{< feature-state for_k8s_version="v1.25" state="stable" >}}
@@ -356,7 +358,7 @@ Cluster Domain | Service (ns/name) | StatefulSet (ns/name) | StatefulSet Domain
356
358
{{< note >}}
357
359
<!--
358
360
Cluster Domain will be set to `cluster.local` unless
359
- [otherwise configured](/docs/concepts/services-networking/dns-pod-service/#how-it-works ).
361
+ [otherwise configured](/docs/concepts/services-networking/dns-pod-service/).
360
362
-->
361
363
集群域会被设置为 `cluster.local`,除非有[其他配置](/zh-cn/docs/concepts/services-networking/dns-pod-service/)。
362
364
{{< /note >}}
@@ -477,8 +479,8 @@ described [above](#deployment-and-scaling-guarantees).
477
479
` Parallel` pod management tells the StatefulSet controller to launch or
478
480
terminate all Pods in parallel, and to not wait for Pods to become Running
479
481
and Ready or completely terminated prior to launching or terminating another
480
- Pod. This option only affects the behavior for scaling operations. Updates are not affected.
481
-
482
+ Pod. This option only affects the behavior for scaling operations. Updates are not
483
+ affected.
482
484
-->
483
485
# ### 并行 Pod 管理 {#parallel-pod-management}
484
486
@@ -487,7 +489,7 @@ Pod. This option only affects the behavior for scaling operations. Updates are n
487
489
这个选项只会影响扩缩操作的行为,更新则不会被影响。
488
490
489
491
<!--
490
- # # Update Strategies
492
+ # # Update strategies
491
493
492
494
A StatefulSet's `.spec.updateStrategy` field allows you to configure
493
495
and disable automated rolling updates for containers, labels, resource request/limits, and
@@ -641,7 +643,9 @@ StatefulSet will then begin to recreate the Pods using the reverted template.
641
643
恢复模板后,还必须删除 StatefulSet 尝试使用错误的配置来运行的 Pod。这样,
642
644
StatefulSet 才会开始使用被还原的模板来重新创建 Pod。
643
645
644
- <!-- # # PersistentVolumeClaim retention -->
646
+ <!--
647
+ # # PersistentVolumeClaim retention
648
+ -->
645
649
# # PersistentVolumeClaim 保留 {#persistentvolumeclaim-retention}
646
650
647
651
{{< feature-state for_k8s_version="v1.23" state="alpha" >}}
@@ -666,7 +670,7 @@ Once enabled, there are two policies you can configure for each StatefulSet:
666
670
` whenScaled`
667
671
: configures the volume retention behavior that applies when the replica count of
668
672
the StatefulSet is reduced; for example, when scaling down the set.
669
-
673
+
670
674
For each policy that you can configure, you can set the value to either `Delete` or `Retain`.
671
675
-->
672
676
` whenDeleted`
@@ -704,7 +708,7 @@ StatefulSet being deleted or scaled down. For example, if a Pod associated with
704
708
fails due to node failure, and the control plane creates a replacement Pod, the StatefulSet
705
709
retains the existing PVC. The existing volume is unaffected, and the cluster will attach it to
706
710
the node where the new Pod is about to launch.
707
-
711
+
708
712
The default for policies is `Retain`, matching the StatefulSet behavior before this new feature.
709
713
710
714
Here is an example policy.
0 commit comments