flypiggyyoyoyo opened a new pull request, #24: URL: https://github.com/apache/incubator-seata-k8s/pull/24
## What is the purpose of the change? The current storage configuration in seata-server-cluster.yaml is incorrectly placed under `spec.store`, which causes deployment failure. The error message shows: "error when creating deploy/seata-server-cluster.yaml: SeataServer in version "v1alpha1" cannot be handled as a SeataServer: strict decoding error: unknown field 'spec.store'". This change moves the storage configuration to the correct location according to the CRD definition. ## Changes ```yaml # Before spec: persistence: volumeReclaimPolicy: Delete store: resources: requests: storage: 5Gi # After spec: persistence: volumeReclaimPolicy: Delete spec: resources: requests: storage: 5Gi ``` ## Testing Results 1. SeataServer resource created successfully: ```bash $ kubectl get seataserver seata-server NAME AGE seata-server 42m ``` 2. PVC created and bound with correct configuration: ```bash $ kubectl get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE seata-store-seata-server-0 Bound pvc-da97f099-2d75-4936-8b56-e0ffb7384dd1 5Gi RWO standard 42m $ kubectl describe pvc seata-store-seata-server-0 Name: seata-store-seata-server-0 Namespace: default StorageClass: standard Status: Bound Capacity: 5Gi Access Modes: RWO VolumeMode: Filesystem ``` 3. StatefulSet status: ```bash $ kubectl get statefulsets -n default NAME READY AGE seata-server 0/1 3m38s ``` ## Checklist - [x] The change is well described and easy to understand - [x] The change addresses a specific issue with the YAML configuration - [x] Manual testing has been performed and results documented - [x] Configuration aligns with CRD definition - [x] Deployment verification completed [中文] ## 修改目的 当前 seata-server-cluster.yaml 中的存储配置错误地放在了 `spec.store` 字段下,导致部署失败。根据 CRD 定义,将存储配置移动到了正确的位置 `persistence.spec` 下。 ## 测试验证 已完成部署测试,验证了 SeataServer 资源创建、PVC 创建和绑定等功能正常。详细测试结果见上述英文描述。 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@seata.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@seata.apache.org For additional commands, e-mail: notifications-h...@seata.apache.org