csi-gcs
secrets-store-csi-driver-provider-gcp
Our great sponsors
csi-gcs | secrets-store-csi-driver-provider-gcp | |
---|---|---|
8 | 6 | |
151 | 224 | |
- | 0.9% | |
3.6 | 7.0 | |
10 months ago | 3 days 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-gcs
-
Google Cloud Storage FUSE
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
- csi-gcs - Kubernetes driver for mounting Google Cloud Storage buckets
- Show HN: Csi-gcs – Kubernetes driver for mounting Google Cloud Storage buckets
-
gitlab runner in kubernetes. readwriteonly is illuding me
I came across this: https://github.com/ofek/csi-gcs Looked super promising - mount a gcs bucket with RWX? giddy up! Of course, when the runner started up my dind container decided to have an aneurism. See output here if you want: https://pastebin.com/N7tKxzwx
secrets-store-csi-driver-provider-gcp
- Bridging the Gap: Leveraging Secret Store CSI Drivers to Access Secrets from Google Secret Manager in GKE Cluster
-
Shhhh... Kubernetes Secrets Are Not Really Secret!
The driver can also sync changes to secrets. The driver currently supports Vault, AWS, Azure, and GCP providers. Secrets Store CSI Driver can also sync provider secrets as Kubernetes secrets; if required, this behavior needs to be explicitly enabled during installation.
-
A better way to manage secrets: reference an external secret defined in the cloud provider environment (please support the idea or give your feedback)
GCP SS-CSI driver
-
How to Inject Secret From Google Secret Manager into GKE Cluster using Helm Chart?
That's interesting actually, Google provides their own rpvider for the Secrets Store CSI Driver: https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp
-
Has anyone here used Secret Manager before?
Consider: if you have a tool like terraform managing your infra components including your data layer, you likely want to manage those reaources in a different lifecycle from your application code. Applications may also likely managed using a different toolset (kubectl, helm, scaffold, etc.). In this case, secret Manager acts as the secure configuration bridge between the tools, keeping the secrets out of human hands. As certs and passwords are generated on the infra side, those values can be stored as secrets in SM. Application workloads - backed by service accounts having access to read the secret - can decrypt during launch and use the secret as needed. You can use common patterns in both GKE (via thesecrets store csi driver ) and Cloud Run for consuming secrets in this way.
-
How to access secrets in GCP secret manager from PODs
I prefer https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp
What are some alternatives?
csi-s3 - A Container Storage Interface for S3
secrets-store-csi-driver - Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume.
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.
Reloader - A Kubernetes controller to watch changes in ConfigMap and Secrets and do rolling upgrades on Pods with their associated Deployment, StatefulSet, DaemonSet and DeploymentConfig – [✩Star] if you're using it!
gcsfuse - A user-space file system for interacting with Google Cloud Storage
aws-efs-csi-driver - CSI Driver for Amazon EFS https://aws.amazon.com/efs/
scribe - Asynchronous data replication for Kubernetes CSI storage
smcache - golang autocert cache implementation for GCP Secret Manager
gcp-compute-persistent-disk-csi-driver - The Google Compute Engine Persistent Disk (GCE PD) Container Storage Interface (CSI) Storage Plugin.
berglas - A tool for managing secrets on Google Cloud
heketi - RESTful based volume management framework for GlusterFS
secrets-store-csi-driver-provider-aws - The AWS provider for the Secrets Store CSI Driver allows you to fetch secrets from AWS Secrets Manager and AWS Systems Manager Parameter Store, and mount them into Kubernetes pods.