gcp-filestore-csi-driver
google-drive-ocamlfuse
gcp-filestore-csi-driver | google-drive-ocamlfuse | |
---|---|---|
2 | 20 | |
82 | 5,370 | |
- | - | |
8.8 | 5.9 | |
about 6 hours ago | 22 days ago | |
Go | OCaml | |
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.
google-drive-ocamlfuse
-
Obsidian didn't sync my files on Debian, any help?
I fixed the problem, it was due to the incorrect setup of the google drive. I followed this guide to set everything up from scratch and create the folder directly in Linux instead of constantly accessing the apparently "encrypted" cloud. If anyone ever runs into the same problem, I really hope this thread is helpful :D
- Google Cloud Storage FUSE
-
Remote Music Folder
You might be able to use something like https://github.com/astrada/google-drive-ocamlfuse
-
What is a good cloud option to sync across Windows and Ubuntu OS's?
Its a little hacky, but google drive with mounted ocaml-fuse kinda does-ish this... though git/GitHub does the trick, too.
-
How to mount Google Drive in a safe way? Open source apps available?
There are fuse drivers like https://github.com/astrada/google-drive-ocamlfuse but I pretty darned sure it's using exactly the same transport protocol as Google's own app.
- Is it possible to automate backup to google drive or similar?
- How do you get google drive working on Ubuntu WITHOUT SNAPD!
-
what app do you use for ..
you might be able to load a drive with locally with google-drive-ocamlfuse but you wouldn't get access to google drives proprietary files (google doc, sheet, slide, etc)
-
10 years since Google said to “hang tight” about Linux support for Google Drive
There's always the excellent unofficial google-drive-ocamlfuse which uses FUSE to mount Google drive to a local directory.
https://github.com/astrada/google-drive-ocamlfuse
-
Cloud Backup apps
Agree with previous comment, dejadup is a good option for local backups, but there isnt a really good backup cloud tool in linux enviroment: https://github.com/vitalif/grive2, https://github.com/astrada/google-drive-ocamlfuse, etc.
What are some alternatives?
gcs-fuse-csi-driver - The Google Cloud Storage FUSE Container Storage Interface (CSI) Plugin.
gcsfuse - A user-space file system for interacting with Google Cloud Storage
gcp-compute-persistent-disk-csi-driver - The Google Compute Engine Persistent Disk (GCE PD) Container Storage Interface (CSI) Storage Plugin.
drive - Google Drive client for the commandline
blob-csi-driver - Azure Blob Storage CSI driver
GDriveFS - An innovative FUSE wrapper for Google Drive.
geesefs - Finally, a good FUSE FS implementation over S3
syncthing-android - Wrapper of syncthing for Android.
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.
VGrive - Google Drive client for linux
extfuse - Extension Framework for FUSE
rclone - "rsync for cloud storage" - Google Drive, S3, Dropbox, Backblaze B2, One Drive, Swift, Hubic, Wasabi, Google Cloud Storage, Azure Blob, Azure Files, Yandex Files