@@ -4201,9 +4201,23 @@ spec:
42014201 volumeClaimTemplates:
42024202 description: |-
42034203 Specifies a list of PersistentVolumeClaim templates that represent the storage requirements for the Component.
4204- Each template specifies the desired characteristics of a persistent volume, such as storage class,
4205- size, and access modes.
4206- These templates are used to dynamically provision persistent volumes for the Component.
4204+
4205+
4206+ Each template defines the desired characteristics of a persistent volume, such as storage class,
4207+ size, and access modes, used for dynamic provisioning.
4208+
4209+
4210+ PVC Adoption Mechanism:
4211+ KubeBlocks supports adopting existing PVCs (static provisioning) if they meet the following criteria
4212+ before the Cluster is created:
4213+ 1. Naming: The PVC name must follow the KubeBlocks naming convention:
4214+ $(vct-name)-$(pod-name) (e.g., "data-mycluster-mysql-0").
4215+ 2. Labeling: The PVC must carry the label "app.kubernetes.io/managed-by=kubeblocks".
4216+ 3. Ownership: The PVC must not have any existing controller reference.
4217+
4218+
4219+ If these conditions are met, KubeBlocks will automatically take over the PVCs and
4220+ set the Component (or its controlled resources) as the owner/controller reference.
42074221 items:
42084222 properties:
42094223 annotations:
@@ -11731,9 +11745,23 @@ spec:
1173111745 volumeClaimTemplates:
1173211746 description: |-
1173311747 Specifies a list of PersistentVolumeClaim templates that represent the storage requirements for the Component.
11734- Each template specifies the desired characteristics of a persistent volume, such as storage class,
11735- size, and access modes.
11736- These templates are used to dynamically provision persistent volumes for the Component.
11748+
11749+
11750+ Each template defines the desired characteristics of a persistent volume, such as storage class,
11751+ size, and access modes, used for dynamic provisioning.
11752+
11753+
11754+ PVC Adoption Mechanism:
11755+ KubeBlocks supports adopting existing PVCs (static provisioning) if they meet the following criteria
11756+ before the Cluster is created:
11757+ 1. Naming: The PVC name must follow the KubeBlocks naming convention:
11758+ $(vct-name)-$(pod-name) (e.g., "data-mycluster-mysql-0").
11759+ 2. Labeling: The PVC must carry the label "app.kubernetes.io/managed-by=kubeblocks".
11760+ 3. Ownership: The PVC must not have any existing controller reference.
11761+
11762+
11763+ If these conditions are met, KubeBlocks will automatically take over the PVCs and
11764+ set the Component (or its controlled resources) as the owner/controller reference.
1173711765 items:
1173811766 properties:
1173911767 annotations:
0 commit comments