aws-efs-csi-driver
vault-csi-provider
aws-efs-csi-driver | vault-csi-provider | |
---|---|---|
11 | 1 | |
683 | 291 | |
1.8% | 2.1% | |
8.5 | 7.9 | |
5 days ago | 9 days ago | |
Go | Go | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
aws-efs-csi-driver
-
Implementing AWS EKS with EFS for dynamic volume provisioning using Terraform. Kubernetes Series - Episode 5
In the past I was have problems with GID allocator, something related to this problem.
-
AWS EFS CSI: Mount Target vs Access Point
However, the docs (https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/master/examples/kubernetes/dynamic_provisioning/README.md) are telling me to create EFS Mount Targets in the EKS subnets. Thats fine.
-
EKS Fargate supports additional Ephemeral Storage
Fargate storage A Pod running on Fargate automatically mounts an Amazon EFS file system. You can't use dynamic persistent volume provisioning with Fargate nodes, but you can use static provisioning. For more information, see Amazon EFS CSI Driver on GitHub.
-
EFS CSI - Dynamic Provisioning and Disaster Recovery?
I guess something like this might go a long way to solve the problem https://github.com/kubernetes-sigs/aws-efs-csi-driver/pull/640 ? Though I see it isn't merged yet
-
Mounting EFS in EKS cluster: example deployment fails
I am currently trying to create an EFS for use within an EKS cluster. I've followed all the instructions, and everything seems to be working for the most part. However, when trying to apply the multiple_pods example deployment from here, the pods cannot succesfully mount the file system. The PV and PVC are both bound and look good, however the pods do not start and yield the following error message:
-
How can 2 deployments using aws-efs-csi-provider share data on the same mount?
In each namespace, create a PV/PVC using the same fixed volume path. See "Volume Path in EKS CSI Driver" To make this work however, you MUST pre-create this volume path in your EFS (I usually just have an EC2 instance with it mounted to work on). From the docs above "Note: this feature requires the sub directory to mount precreated on EFS before consuming the volume from"
- Confused about kubernetes storage
-
Confused abut EKS gp2 default storage class - can i use it or not?
resource "aws_iam_policy" "eks_efs_csi_driver_policy" { # https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/master/docs/iam-policy-example.json policy = file("./6.AWSEFSpolicy.json") name = "aws-efs-csi-policy" }
- How is a PersistentVolumeClaim consistent?
-
EKS IAM Deep Dive
efs - IAM Policy for AWS EFS CSI Driver.
vault-csi-provider
-
Inject Secrets into your Pod Environments at the Container Runtime
Why not use https://github.com/kubernetes-sigs/secrets-store-csi-driver to do this? Then you don't have a strict binding to runc. A live example of using the CSI driver with a secrets provider is https://github.com/hashicorp/vault-csi-provider
What are some alternatives?
ceph-csi - CSI driver for Ceph
bank-vaults - A Vault swiss-army knife: A CLI tool to init, unseal and configure Vault (auth methods, secret engines).
aws-ebs-csi-driver - CSI driver for Amazon EBS https://aws.amazon.com/ebs/
secrets-store-csi-driver - Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume.
kiam - Integrate AWS IAM with Kubernetes
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.
secrets-store-csi-driver-provider-gcp - Google Secret Manager provider for the Secret Store CSI Driver.
topolvm - Capacity-aware CSI plugin for Kubernetes
aws-load-balancer-controller - A Kubernetes controller for Elastic Load Balancers
azurefile-csi-driver - Azure File CSI Driver
amazon-cloudwatch-agent - CloudWatch Agent enables you to collect and export host-level metrics and logs on instances running Linux or Windows server.
vault-creds - Sidecar container for requesting dynamic Vault database secrets