Bryant Biggs

Hi @Hokwang - correct, the current implementation for the `aws-ebs-csi-driver` is through an EKS managed addon. We can look at providing an alternate route for deploying/managing through a Helm chart...

> I think that all addons including vpc-cni will be removed. Because it is a prerequisite for installing other cni. So if some addon has installing helm way, it is...

Thank you for the request @andrewhibbert ! Would you mind sharing how you manage this in your cluster today? Do you manually remove the EKS provided VPC CNI plugin and...

Thank you for sharing that info @andrewhibbert - there are a number of similar tickets on the containers roadmap where users are looking for various alternative means of handling the...

> @bryantbiggs I'm not sure if this relevant to this but it seems that the custom value I set through amazon_eks_vpc_cni_config doesn't get applied to the running DaemonSet, I want...

any updates on this - is it even on the roadmap @medikoo ? #3421 #3696 #4715 #5150 #6145 #7085 tl;dr - I think all are looking for serverless to be...

How do either of those policies work without `iam:CreateRole`? If Chalice is creating/managing the role on your behalf, access to this resource would be a must

For anyone landing here - this issue is not related to the Kubernetes provider 1. EKS Managed node groups and Fargate profiles will automatically create an aws-auth configmap in the...

Please raise a ticket through AWS to request guidance. This module does not handle scheduling; it just interacts with the API provided through the provider.

hmm, looks like best we could do would be to add a conditional filter for `tag` https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeVpcEndpointServices.html