Skip to content

feat: Add base manifests to deploy vsphere-csi #46

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mikeruu merged 2 commits into from
Dec 5, 2025
Merged

feat: Add base manifests to deploy vsphere-csi #46

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
79f67f0
feat: Add base manifests to deploy vsphere-csi
pratik705 Dec 3, 2025
270a430
Merge branch 'main' into vsphere-csi-driver
mikeruu Dec 5, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions applications/base/services/vsphere-csi/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
# vSphere CSI – Base Configuration

This directory contains the base manifests for deploying the vSphere Cloud Storage Interface (CSI) driver, enabling Kubernetes clusters running on VMware vSphere to provision and manage persistent storage natively.
It is designed to be consumed by cluster repositories as a remote base, allowing each cluster to apply custom overrides such as StorageClass definitions, topology settings, or credentials.

**About vSphere CSI:**

- Provides dynamic provisioning of PersistentVolumes (PVs) backed by vSphere datastores including vSAN, VMFS, and NFS.
- Supports advanced features such as volume expansion, snapshots, and cloning.
- Integrates with vSphere Storage Policy Based Management (SPBM) so Kubernetes PVCs can inherit vSphere storage policies.
- Enables topology-aware provisioning, ensuring volumes are created in the appropriate zone or failure domain for workload placement.
- Offloads volume lifecycle operations to vSphere, improving reliability, consistency, and automation.
Loading