gcp-filestore-csi-driver
rclone
gcp-filestore-csi-driver | rclone | |
---|---|---|
2 | 963 | |
82 | 43,959 | |
- | 1.3% | |
8.8 | 9.8 | |
7 days ago | 3 days ago | |
Go | Go | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gcp-filestore-csi-driver
-
Google Cloud Storage FUSE
Hi Ofek,
I am a contributor who works on the Google Cloud Storage FUSE CSI Driver project. The project is partially inspired by your CSI implementation. Thank you so much for the contribution to the Kubernetes community. However, I would like to clarify a few things regarding your post.
The Cloud Storage FUSE CSI Driver project does not have “in large part copied code” from your implementation. The initial commit you referred to in the post was based on a fork of another open source project: https://github.com/kubernetes-sigs/gcp-filestore-csi-driver. If you compare the Google Cloud Storage FUSE CSI Driver repo with the Google Cloud Filestore CSI Driver repo, you will notice the obvious similarities, in terms of the code structure, the Dockerfile, the usage of Kustomize, and the way the CSI is implemented. Moreover, the design of the Google Cloud Storage FUSE CSI Driver included a proxy server, and then evolved to a sidecar container mode, which are all significantly different from your implementation.
As for the Dockerfile annotations you pointed out in the initial commit, I did follow the pattern in your repo because I thought it was the standard way to declare the copyright. However, it didn't take me too long to realize that the Dockerfile annotations are not required, so I removed them.
Thank you again for your contribution to the open source community. I have included your project link on the readme page. I take the copyright very seriously, so please feel free to directly create issues or PRs on the Cloud Storage FUSE CSI Driver GitHub project page if I missed any other copyright information.
-
Introduction to Day 2 Kubernetes
Any Kubernetes cluster requires persistent storage - whether organizations choose to begin with an on-premise Kubernetes cluster and migrate to the public cloud, or provision a Kubernetes cluster using a managed service in the cloud. Kubernetes supports multiple types of persistent storage – from object storage (such as Azure Blob storage or Google Cloud Storage), block storage (such as Amazon EBS, Azure Disk, or Google Persistent Disk), or file sharing storage (such as Amazon EFS, Azure Files or Google Cloud Filestore). The fact that each cloud provider has its implementation of persistent storage adds to the complexity of storage management, not to mention a scenario where an organization is provisioning Kubernetes clusters over several cloud providers. To succeed in managing Kubernetes clusters over a long period, knowing which storage type to use for each scenario, requires storage expertise.
rclone
-
Supabase Storage: now supports the S3 protocol
rclone: a command-line program to manage files on cloud storage.
- World Backup Day
-
S3 Client against disasters (hacks, fires, catastrophes)
Synchronise buckets with Sclone or Rclone
- Show HN: Query Your Sheets with SheetSQL
-
Rclone syncs your files to cloud storage
Says that Apple doesn't provide a multi platform API. It doesn't provide any official supported way to access iCloud from Windows, Linux.
There's a ticket covering everything you might ever want to know:
https://github.com/rclone/rclone/issues/1778
-
Ask HN: Best modern file transfer/synchronization protocol?
seconding rsync and syncthing.
the server could expose an smb or nfs share, the client could mount it, and then sync to that mount.
rsync over ssh also works, if you do not want to run smb/nfs.
this is also a cool tool https://rclone.org/
-
Ask HN: How do you do personal backups in 2023? (Google and Dropbox issues)
rclone [1] to dropbox. works since years without problems
[1] https://rclone.org/
-
Which synchronization tool are you using together with the pCloud Crypto Folder?
rclone provides a special pCloud config option, which makes the setup straight forward. rclone can encrypt the data it uploads with its own encryption but not with the pCloud encryption. Therefore it can only upload data to the unencrypted pCloud folders, not to the Crypto Folder.
- Backup of Google Drive (and photos?) to local disk (not to Google Drive)
-
All I want for Christmas is
The arkclone project impliments rclone in ArkOS to achieve cloud saves. Not yet built in to ArkOS yet, and not a lot of recent traction on the pull request to get it added, but it can be installed manually.
What are some alternatives?
gcs-fuse-csi-driver - The Google Cloud Storage FUSE Container Storage Interface (CSI) Plugin.
syncthing - Open Source Continuous File Synchronization
gcp-compute-persistent-disk-csi-driver - The Google Compute Engine Persistent Disk (GCE PD) Container Storage Interface (CSI) Storage Plugin.
Cryptomator - Multi-platform transparent client-side encryption of your files in the cloud
blob-csi-driver - Azure Blob Storage CSI driver
rsync - An open source utility that provides fast incremental file transfer. It also has useful features for backup and restore operations among many other use cases.
geesefs - Finally, a good FUSE FS implementation over S3
s3fs-fuse - FUSE-based file system backed by Amazon S3
curve - Curve is a sandbox project hosted by the CNCF Foundation. It's cloud-native, high-performance, and easy to operate. Curve is an open-source distributed storage system for block and shared file storage.
Duplicati - Store securely encrypted backups in the cloud!
google-drive-ocamlfuse - FUSE filesystem over Google Drive
aws-cli - Universal Command Line Interface for Amazon Web Services