amazon-cloudwatch-agent
aws-efs-csi-driver
amazon-cloudwatch-agent | aws-efs-csi-driver | |
---|---|---|
2 | 11 | |
406 | 683 | |
1.5% | 0.4% | |
9.4 | 8.5 | |
2 days ago | 3 days ago | |
Go | Go | |
MIT License | 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.
amazon-cloudwatch-agent
- Amazon Linux 2022 Coming
-
EKS IAM Deep Dive
cloudWatch - IAM Policy CloudWatchAgentServerPolicy for AWS Cloudwatch Agent.
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.
What are some alternatives?
amazon-ssm-agent - An agent to enable remote management of your EC2 instances, on-premises servers, or virtual machines (VMs).
ceph-csi - CSI driver for Ceph
aws-xray-daemon - The AWS X-Ray daemon listens for traffic on UDP port 2000, gathers raw segment data, and relays it to the AWS X-Ray API.
vault-csi-provider - HashiCorp Vault Provider for Secret Store CSI Driver
amazon-ecs-agent - Amazon Elastic Container Service Agent
aws-ebs-csi-driver - CSI driver for Amazon EBS https://aws.amazon.com/ebs/
amazon-linux-2023 - Amazon Linux 2023
kiam - Integrate AWS IAM with Kubernetes
aws-app-mesh-controller-for-k8s - A controller to help manage App Mesh resources for a Kubernetes cluster.
secrets-store-csi-driver-provider-gcp - Google Secret Manager provider for the Secret Store CSI Driver.
aws-load-balancer-controller - A Kubernetes controller for Elastic Load Balancers