Apoorva Kulkarni

@vara-bonthu can you please confirm we have this implemented [here](https://github.com/aws-ia/terraform-aws-eks-blueprints/blob/c459a963d92f11b41f4c9fc5f40c7a279fe01be1/variables.tf#L184)?

Also see https://github.com/aws/amazon-vpc-cni-k8s/issues/1447

Hi @spkane, agree that minimum we should document this. So for k8s resources being created by argocd, they need to be cleaned up first before doing the terraform destroy. Not...

AMG being outside the EKS cluster does not fit well as an add-on. We do have example of how to provision a Prometheus, AMP, AMG stack [here](https://github.com/aws-ia/terraform-aws-eks-blueprints/tree/main/examples/observability/amp-amg-opensearch). But for those...

Re-purposing this ticket to add support for [Grafana Agent](https://grafana.com/docs/agent/latest/)

Hi @niv1612, as demonstrated in this [blog](https://aws.amazon.com/blogs/containers/monitoring-amazon-eks-on-aws-fargate-using-prometheus-and-grafana/) the recommendation is to deploy Prometheus on at least 1 worker node. Another option is to use [ADOT](https://aws-observability.github.io/aws-o11y-recipes/recipes/fargate-eks-metrics-go-adot-ampamg/) to scrape the metrics and...

Thanks @ruzickap for raising this issue. @ricardosouzamorais any updates on the PR?

Thanks @schwichti for your feature request. I've created https://github.com/aws-ia/terraform-ssp-amazon-eks/issues/186 for tracking.

@kahirokunn thanks for the PR. Can you please open an issue for tracking and add steps to reproduce as well as results of your testing after applying this fix?

@florentio that would be awesome! Let us discuss here on what you are planning to do.