aboutsummaryrefslogtreecommitdiff
path: root/deploy
AgeCommit message (Collapse)AuthorFilesLines
2022-09-07fix sock pathCristian Chiru1-3/+3
2022-09-07bump chart versionCristian Chiru1-1/+1
2022-09-07add non standard volumes for seaweedfs-csi-driver node; improve helm textsCristian Chiru2-7/+13
2022-09-05Allow per pv/pvc settings for cache, concurrent writes and uid/gid mapsViktor Kuzmin1-0/+5
2022-07-07Pods using the same volume share mountgarenchan1-0/+7
2022-06-05Fix broken Helm templateBryce Lampe2-8/+31
2022-04-26Allow to set tolerations and affinity for both node and controllerViktor Kuzmin3-2/+18
2022-04-18Hashicorp Nomad deploy exampleMateusz Kondej5-0/+465
2022-04-15fix VolumeExpansion not workjoy7174-0/+27
2022-03-18capacity is enforcedchrislu1-1/+1
2022-02-22This updates the helm chart, and the pre-generated manifest.Thomas Davis3-251/+634
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.
2022-02-15use env to config log verbositygarenchan2-6/+8
2021-10-09Allow to specify image pull secrets for private repositoryViktor Kuzmin2-0/+11
2021-09-28Merge pull request #33 from kvaster/static_mountsChris Lu1-1/+2
2021-09-28Allow static persistent volumes, some code cleanupViktor Kuzmin1-1/+2
2021-09-28Update for 1.22 - fixes seaweedfs/seaweedfs-csi-driver#36Russell Smith1-21/+28
2021-09-20Fix logging verbosity optionsViktor Kuzmin3-0/+7
2021-08-20add explicit uid and gid mappingChris Lu1-0/+12
2021-05-28Remove extraneous parameter in StatefulSetPaul Dubs1-2/+0
2021-05-28Remove extraneous parameter for weed in DaemonSetPaul Dubs1-1/+0
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-02-18Merge remote-tracking branch 'origin/master' into helmUstuzhanin Anton3-3/+3
# Conflicts: # README.md
2021-02-18feat: custom updateStrategy for deamonsetUstuzhanin Anton4-4/+11
2021-02-16adjustChris Lu3-3/+3
2021-02-16feat: add helm chertUstuzhanin Anton1-0/+1
2021-02-02feat: fix helm chertUstuzhanin Anton9-53/+112
2021-01-22feat: add helm chertUstuzhanin Anton9-0/+469
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 Lu4-102/+411
2020-06-01configure filer via CLIChris Lu1-0/+102