aboutsummaryrefslogtreecommitdiff
path: root/deploy/kubernetes/seaweedfs-csi.yaml
AgeCommit message (Collapse)AuthorFilesLines
14 daysfix: use :dev tag instead of :latest for static manifestschrislusf1-3/+3
Using :latest in static manifests can lead to unpredictable behavior. The :dev tag signals this is a development version and is more appropriate for version-controlled manifests.
14 daysfix: use :latest tag and replace deprecated IsMountPointchrislusf1-3/+3
- Change image tags from :dev to :latest in seaweedfs-csi.yaml for predictable production deployments - Replace deprecated IsMountPoint with IsLikelyNotMountPoint for consistency with k8s.io/mount-utils recommendations
14 daysfix: address gemini review - OnDelete strategy and log invalid endpointchrislusf1-3/+3
- Change seaweedfs-mount DaemonSet updateStrategy from RollingUpdate to OnDelete in seaweedfs-csi.yaml for consistency with values.yaml (safer for active mounts) - Add warning log when invalid mountEndpoint is provided to aid debugging
14 daysfix: address code review feedbackchrislusf1-3/+3
- CRITICAL: Make socket path configurable based on mountEndpoint - Added volumeSocketDir field to SeaweedFsDriver - LocalSocketPath now accepts baseDir parameter - Derived from mountEndpoint for user-configurable socket paths - HIGH: Pin seaweedfs version in Dockerfiles for reproducible builds - Added SEAWEEDFS_VERSION build arg (default: 3.80) - Clone specific tag instead of master - HIGH: Fix Dockerfile.dev to use local context instead of personal fork - Removed hardcoded zemul/seaweedfs-csi-driver clone - Now uses COPY . . for local development - HIGH: Change :latest to :dev in kubernetes manifests - Mutable :latest tag replaced with :dev for predictability - MEDIUM: Remove Aliyun mirror from Dockerfile.dev - Region-specific mirrors shouldn't be in general-purpose files - MEDIUM: Improve error handling in client.go - Now reports read errors when failing to read error response body - MEDIUM: Fix inconsistent error return in manager.go - Return nil instead of empty struct on error (Go idiom)
14 daysadd: merge prepare params.泽淼 周1-3/+3
14 daysfix: seaweedfs-csi.yaml volumes config泽淼 周1-11/+29
14 daysadjust: Dockerfile泽淼 周1-2/+2
14 daysfix: seaweefs-mount image泽淼 周1-1/+1
14 daysfeat: seaweedfs-mount daemonset泽淼 周1-0/+57
2024-12-15fix k8s deploy argsliguowei1-2/+2
2023-08-07Helm chart refactoringViktor Kuzmin1-138/+260
* Separate NodeServer and ControllerServer * Allow leader election for sidecars and replica count fot controller component * Liveness probes * Allow disabling attacher, cause this functionality is not used in reality
2022-11-16Do not define namespace in seaweedfs-csi.yamlArtur Motyka1-5/+0
2022-06-05Fix broken Helm templateBryce Lampe1-2/+26
2022-02-22This updates the helm chart, and the pre-generated manifest.Thomas Davis1-247/+198
The values.yaml is updated to use the latest sig-storage CSI containers from the following urls: https://kubernetes-csi.github.io/docs/node-driver-registrar.html https://kubernetes-csi.github.io/docs/external-provisioner.html https://kubernetes-csi.github.io/docs/external-attacher.html These URL points to the supported version tables.
2021-09-28Update for 1.22 - fixes seaweedfs/seaweedfs-csi-driver#36Russell Smith1-21/+28
2021-08-20add explicit uid and gid mappingChris Lu1-0/+12
2021-04-11support configurable cache directoryChris Lu1-0/+6
fix https://github.com/seaweedfs/seaweedfs-csi-driver/issues/20
2021-04-11support configurable cache sizeChris Lu1-0/+6
fix https://github.com/seaweedfs/seaweedfs-csi-driver/issues/20
2021-01-11update to latestChris Lu1-13/+15
fix https://github.com/seaweedfs/seaweedfs-csi-driver/issues/7
2020-10-02Update CSI yaml to allow using k8s service DNS to contact the filerHarry Brundage1-2/+3
I think lots of users are going to use the CSI driver with a seaweedfs cluster also running in k8s. The natural way to connect the driver to that cluster would be using DNS instead of hard coded IPs, so I set `SEAWEEDFS_FILER` to something like `seaweedfs-filer.seaweed-namespace.svc:8888`, which the driver kept timing out trying to connect. I realized the driver was running using `hostNetwork: true`, which means the in-cluster DNS resolution doesn't happen, so the .svc hostnames are just unresolved. This changes the default YAML for the next person coming along to use the in-cluster DNS resolution first, and then the host's DNS resolution, so that if the filer happens to be running the cluster, it can be connected from the driver running on the host. An alternative would be to not use `hostNetworking` for the driver daemonset, but I am presuming that's there for a reason.
2020-09-03add timeoutChris Lu1-0/+1
2020-06-09skip checkingChris Lu1-4/+17
2020-06-07copied from moosefsChris Lu1-0/+384
generated by cgit v1.2.3 (git 2.25.1) at 2025-12-20 22:15:35 +0000