James Chan

I created a ticket with AWS support and confirmed that we can update the strategies afterward to the auto-scaling groups automatically generated when node groups are created. So, it would...

Any updates on this? I'd love to update to the latest available. :)

I'm glad I'm not the only one seeing this weird behavior. The cluster is determined to be replaced when I executed "terraform apply", but the destroy didn't happen and it...

I also tried Helm deployment through Terraform but was still hit with the same issue. ``` resource "helm_release" "external_dns" { name = "external-dns" repository = "https://kubernetes-sigs.github.io/external-dns" chart = "external-dns" create_namespace...

Is this something new in v0.15.0 because I have no issues with v0.14.2?

Unfortunately, the container doesn't seem to have shell and curl installed.

I have some updates. It looks like this is only happening in the us-east-1 region. I have similar deployments in ap-southeast-1, eu-central-1, and ca-central-1, but they all came up normally.

> /help /area provider/aws > > Does it mean helm chart version `0.14.2` works with no issues in `us-east-1`? What about AWS IAM permissions? Any restrictions, it most likely safe...

Another finding is that if I incorrectly set the AWS_DEFAULT_REGION to us-east-1 in an AWS account servicing a different region (e.g. ap-southeast-2), the external-dns runs without the failed to list...

We are still seeing the error with the v0.18.0 release. Since this is a private VPC, is there any regional VPC endpoint required to be set up to allow access?...