aws-ebs-csi-driver
CSI driver for Amazon EBS https://aws.amazon.com/ebs/ (by kubernetes-sigs)
aws-efs-csi-driver
CSI Driver for Amazon EFS https://aws.amazon.com/efs/ (by kubernetes-sigs)
aws-ebs-csi-driver | aws-efs-csi-driver | |
---|---|---|
13 | 11 | |
920 | 683 | |
1.7% | 0.4% | |
9.4 | 8.5 | |
6 days ago | 6 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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-ebs-csi-driver
Posts with mentions or reviews of aws-ebs-csi-driver.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-05.
-
AWS EBS CSI driver
The AWS EBS CSI Driver relies on IAM permissions to communicate with Amazon EBS for volume management on behalf of the user. The example policy can be used to define the required permissions. Additionally, AWS provides a managed policy at ARN arn:aws:iam::aws:policy/service-role/AmazonEBSCSIDriverPolicy
-
PV/PVC Not working after k8s upgrade to 1.25
I looks like the driver's permissions to invoke the EBS APIs was revoked and/or changed. When you install the EBS CSI addon you can either inherit permissions from the worker node or you can choose an IRSA role (preferred). If you use IRSA, the service account that the EBS CSI driver uses should have an annotation that references the ARN of the IAM role you selected, e.g. eks.amazonaws.com/role-arn: arn:aws:iam::111122223333:role/my-role. You can see an example of the IAM policy the driver needs here, https://github.com/kubernetes-sigs/aws-ebs-csi-driver/blob/fb6d456558fb291b13f855454c1525c7acaf7046/docs/example-iam-policy.json.
- Confused about kubernetes storage
-
Unable to Access AWS EKS Cluter after creating using Terraform
I'm know it's possible to write terraform code that exhibits that issue, but that's not the case in my experience. I'm using helm to deploy aws's ebs csi driver in the above setup. As you mentioned, if the eks cluster was destroyed before the helm provider attempted to use its API to destroy the helm deployment, it would cause problems. And I don't run into that issue. It's not luck of timing, either - I also have a CI process that deploys all of this, tests, and deletes it all that has succeeded hundreds of times.
-
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.
-
Dealing with EC2 Instance volume limits in EKS
Lots of info in this issue: https://github.com/kubernetes-sigs/aws-ebs-csi-driver/issues/1163
-
Help me understand real use cases of k8s, I can’t wrap my head around it
aws-ebs-csi-driver
- How is a PersistentVolumeClaim consistent?
-
EKS PVC <-> EBS volume associations after cluster recreation
Hello, we are running an EKS cluster (1.20) with aws-ebs-csi-driver (1.4.0). After recreating our whole cluster we can observe that the EBS volumes from our PVCs still exist but the "mapping" to the PVCs is gone.
-
A PVC Operator which Uploads Data to S3 on Delete and Downloads on Create
OP could probably just layer their own CSI driver on top of an existing one (a la aws-ebs-csi-driver), but there's still several problems:
aws-efs-csi-driver
Posts with mentions or reviews of aws-efs-csi-driver.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-14.
-
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.
What are some alternatives?
When comparing aws-ebs-csi-driver and aws-efs-csi-driver you can also consider the following projects:
autoscaler - Autoscaling components for Kubernetes
ceph-csi - CSI driver for Ceph
vault-csi-provider - HashiCorp Vault Provider for Secret Store CSI Driver
aws-load-balancer-controller - A Kubernetes controller for Elastic Load Balancers
kiam - Integrate AWS IAM with Kubernetes
topolvm - Capacity-aware CSI plugin for Kubernetes
secrets-store-csi-driver-provider-gcp - Google Secret Manager provider for the Secret Store CSI Driver.
descheduler - Descheduler for Kubernetes
aws-iam-authenticator - A tool to use AWS IAM credentials to authenticate to a Kubernetes cluster
amazon-cloudwatch-agent - CloudWatch Agent enables you to collect and export host-level metrics and logs on instances running Linux or Windows server.
aws-ebs-csi-driver vs autoscaler
aws-efs-csi-driver vs ceph-csi
aws-ebs-csi-driver vs ceph-csi
aws-efs-csi-driver vs vault-csi-provider
aws-ebs-csi-driver vs aws-load-balancer-controller
aws-efs-csi-driver vs kiam
aws-ebs-csi-driver vs topolvm
aws-efs-csi-driver vs secrets-store-csi-driver-provider-gcp
aws-ebs-csi-driver vs descheduler
aws-efs-csi-driver vs aws-load-balancer-controller
aws-ebs-csi-driver vs aws-iam-authenticator
aws-efs-csi-driver vs amazon-cloudwatch-agent