From acdf12bd01fd9b172a713950b0d2cbef132b2ba7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E6=9D=A8=E5=86=9B10092085?= Date: Mon, 5 Aug 2024 21:30:25 +0800 Subject: [PATCH] Updated incorrect description of persistentVolumeClaimRetentionPolicy Kubernetes-commit: 56bbae4807989cd43eff17cf9fa93f7b54c087bd --- testdata/openapi/v3/apis/apps/v1.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/testdata/openapi/v3/apis/apps/v1.json b/testdata/openapi/v3/apis/apps/v1.json index 1fc9d1c4..c49ca798 100644 --- a/testdata/openapi/v3/apis/apps/v1.json +++ b/testdata/openapi/v3/apis/apps/v1.json @@ -1086,7 +1086,7 @@ "$ref": "#/components/schemas/io.k8s.api.apps.v1.StatefulSetPersistentVolumeClaimRetentionPolicy" } ], - "description": "persistentVolumeClaimRetentionPolicy describes the lifecycle of persistent volume claims created from volumeClaimTemplates. By default, all persistent volume claims are created as needed and retained until manually deleted. This policy allows the lifecycle to be altered, for example by deleting persistent volume claims when their stateful set is deleted, or when their pod is scaled down. This requires the StatefulSetAutoDeletePVC feature gate to be enabled, which is alpha. +optional" + "description": "persistentVolumeClaimRetentionPolicy describes the lifecycle of persistent volume claims created from volumeClaimTemplates. By default, all persistent volume claims are created as needed and retained until manually deleted. This policy allows the lifecycle to be altered, for example by deleting persistent volume claims when their stateful set is deleted, or when their pod is scaled down. This requires the StatefulSetAutoDeletePVC feature gate to be enabled. +optional" }, "podManagementPolicy": { "description": "podManagementPolicy controls how pods are created during initial scale up, when replacing pods on nodes, or when scaling down. The default policy is `OrderedReady`, where pods are created in increasing order (pod-0, then pod-1, etc) and the controller will wait until each pod is ready before continuing. When scaling down, the pods are removed in the opposite order. The alternative policy is `Parallel` which will create pods in parallel to match the desired scale without waiting, and on scale down will delete all pods at once.",