feat(server): support static provisioning PV for k8s PVC volumes#916
feat(server): support static provisioning PV for k8s PVC volumes#916yoogoc wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bcde2194c4
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
bcde219 to
5d4d22d
Compare
|
Changed directories: kubernetes、sdks、server、specs. 📋 Recommended labels (based on changed files):
Other available labels:
💡 Tip: Use cc @yoogoc |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5d4d22d450
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
5d4d22d to
cc1eee7
Compare
Summary
Some Kubernetes environments lack dynamic provisioning (e.g., bare-metal clusters without a CSI driver, or scenarios requiring pre-existing NFS/hostPath/local volumes). Static provisioning allows users to specify the exact PV spec (e.g., NFS server, hostPath, CSI volumeHandle) so the server creates and binds both the PV and PVC automatically, without needing a StorageClass provisioner.
Testing
Breaking Changes
Checklist