Guillaume Legrain
Guillaume Legrain
Hi, having the same issue, could be cool if datashim could support deployement !
```yaml resource "aws_iam_policy" "ebs_policy" { provider = aws.main name = "AmazonEKS_EBS_CSI_Driver_Policy" path = "/" description = "Policy for EBS on Kubernetes" depends_on = [module.eks] policy =
``` resource "aws_eks_addon" "ebs_csi" { provider = aws.main cluster_name = local.cluster_name addon_name = "aws-ebs-csi-driver" service_account_role_arn = aws_iam_role.ebs_roles.arn depends_on = [module.eks] } ```
Just push a request to our AWS Solution Architect and other contact on AWS. Let's see if they can do something to push this issue faster
Create an image that could expose tools information as metrics on an endpoint so we could grab them through prometheus and expose them on Grafana could be a very good...
@x4m > Hi! You can archive empty file Can you explain what this mean ? Create a fake wal, compress in lz4 and push it on s3 ? What would...
Would it be possible to re-open this as it hasnt been corrected yet ....
I think it has been implemented in : https://github.com/aminueza/terraform-provider-minio/pull/594
@JelteF yes exactly, the memory usage is growing according to the number of pools. Thanks for your anwser