csi-s3
csi-gcs
Our great sponsors
csi-s3 | csi-gcs | |
---|---|---|
3 | 8 | |
731 | 149 | |
- | - | |
0.0 | 3.6 | |
6 months ago | 9 months ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
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.
csi-s3
-
Learning K3s at Home, troubles with S3 Storage
This is the repo I am trying to use to setup s3 storage for config files of services.
-
Question: does anyone know Storage Provider with S3 as persistence layer?
Could just use an S3 as the storage and handle backups with other tools against the bucket. https://github.com/ctrox/csi-s3
-
How to scale nginx pod when pod is mounting a volume
You could also use the s3fs CSI for your storage. There may be some learning curve to getting it working. My only word of advise is to use the examples in the repo, the README.md is stale. I made some notes here.
csi-gcs
-
Google Cloud Storage FUSE
I do appreciate that Google is now officially supporting gcsfuse because it genuinely is a great project. However, their Kubernetes CSI driver seems to have in large part copied code from the one I and a co-maintainer have been working on for years:
- https://github.com/GoogleCloudPlatform/gcs-fuse-csi-driver
- https://github.com/ofek/csi-gcs
Here is the initial commit: https://github.com/GoogleCloudPlatform/gcs-fuse-csi-driver/c...
Notice for example not just the code but also the associated files. In the Dockerfile it blatantly copied the one from my repo, even the dual license I chose because I was very into Rust at the time. Or take a look at the deployment examples which use Kustomize which I like but is very uncommon and most Kubernetes projects provide Helm charts instead.
They were most certainly aware of the project because Google reached out to discuss potential collaboration but never responded back: https://imgur.com/a/KDuf9mj
You licensed the code as MIT - https://github.com/ofek/csi-gcs/blob/master/LICENSE-MIT
Are you saying you have an issue with them copying your MIT licensed code?
You're right their Apache licenses are different:
https://github.com/ofek/csi-gcs/blob/master/LICENSE-APACHE
https://github.com/GoogleCloudPlatform/gcs-fuse-csi-driver/b...
OP should submit a PR to correct this. IANAL but pretty sure they're supposed to use the original copy including copyright notice "Copyright 2020 Ofek Lev"
-
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.
- csi-gcs - CSI driver for mounting Google Cloud Storage buckets
What are some alternatives?
nfs-subdir-external-provisioner - Dynamic sub-dir volume provisioner on a remote NFS server.
nfs-ganesha-server-and-external-provisioner - NFS Ganesha Server and Volume Provisioner.
kubemq-bridges - KubeMQ Bridges bridge, replicate, aggregate, and transform messages between KubeMQ clusters no matter where they are, allowing to build a true cloud-native messaging single network running globally.
secrets-store-csi-driver-provider-gcp - Google Secret Manager provider for the Secret Store CSI Driver.
topolvm - Capacity-aware CSI plugin for Kubernetes
gcsfuse - A user-space file system for interacting with Google Cloud Storage
Gitkube - Build and deploy docker images to Kubernetes using git push
scribe - Asynchronous data replication for Kubernetes CSI storage
s3sync - ♻️ Golang utility for syncing between s3 and local, similar to `aws s3 sync`
k9s - 🐶 Kubernetes CLI To Manage Your Clusters In Style!
ceph-csi - CSI driver for Ceph
kubernetes-operator-roiergasias - 'Roiergasias' kubernetes operator is meant to address a fundamental requirement of any data science / machine learning project running their pipelines on Kubernetes - which is to quickly provision a declarative data pipeline (on demand) for their various project needs using simple kubectl commands. Basically, implementing the concept of No Ops. The fundamental principle is to utilise best of docker, kubernetes and programming language features to run a workflow with minimal workflow definition syntax. It is a Go based workflow running on command line or Kubernetes with the help of a custom operator for a quick and automated data pipeline for your machine learning projects (a flavor of MLOps).