@@ -4482,9 +4482,23 @@ spec:
44824482 volumeClaimTemplates:
44834483 description: |-
44844484 Specifies a list of PersistentVolumeClaim templates that represent the storage requirements for the Component.
4485- Each template specifies the desired characteristics of a persistent volume, such as storage class,
4486- size, and access modes.
4487- These templates are used to dynamically provision persistent volumes for the Component.
4485+
4486+
4487+ Each template defines the desired characteristics of a persistent volume, such as storage class,
4488+ size, and access modes, used for dynamic provisioning.
4489+
4490+
4491+ PVC Adoption Mechanism:
4492+ KubeBlocks supports adopting existing PVCs (static provisioning) if they meet the following criteria
4493+ before the Cluster is created:
4494+ 1. Naming: The PVC name must follow the KubeBlocks naming convention:
4495+ $(vct-name)-$(pod-name) (e.g., "data-mycluster-mysql-0").
4496+ 2. Labeling: The PVC must carry the label "app.kubernetes.io/managed-by=kubeblocks".
4497+ 3. Ownership: The PVC must not have any existing controller reference.
4498+
4499+
4500+ If these conditions are met, KubeBlocks will automatically take over the PVCs and
4501+ set the Component (or its controlled resources) as the owner/controller reference.
44884502 items:
44894503 properties:
44904504 annotations:
@@ -15841,9 +15855,23 @@ spec:
1584115855 volumeClaimTemplates:
1584215856 description: |-
1584315857 Specifies a list of PersistentVolumeClaim templates that represent the storage requirements for the Component.
15844- Each template specifies the desired characteristics of a persistent volume, such as storage class,
15845- size, and access modes.
15846- These templates are used to dynamically provision persistent volumes for the Component.
15858+
15859+
15860+ Each template defines the desired characteristics of a persistent volume, such as storage class,
15861+ size, and access modes, used for dynamic provisioning.
15862+
15863+
15864+ PVC Adoption Mechanism:
15865+ KubeBlocks supports adopting existing PVCs (static provisioning) if they meet the following criteria
15866+ before the Cluster is created:
15867+ 1. Naming: The PVC name must follow the KubeBlocks naming convention:
15868+ $(vct-name)-$(pod-name) (e.g., "data-mycluster-mysql-0").
15869+ 2. Labeling: The PVC must carry the label "app.kubernetes.io/managed-by=kubeblocks".
15870+ 3. Ownership: The PVC must not have any existing controller reference.
15871+
15872+
15873+ If these conditions are met, KubeBlocks will automatically take over the PVCs and
15874+ set the Component (or its controlled resources) as the owner/controller reference.
1584715875 items:
1584815876 properties:
1584915877 annotations:
0 commit comments