Ivan Sukhomlyn

It would nice to have such a Terraform resource to patch EKS `aws-node` DaemonSet with a custom ServiceAccount. For example, in the case of the IRSA approach usage for Pods...

@emanor-okta For example, I had the same issue at the okta.com organization, not a preview. More details https://github.com/okta/terraform-provider-okta/issues/953#issuecomment-1141099192

I have the same situation with the `2.15` version. CW Log Group is in a stuck state. Logs: ``` 13:35:15 us-west-2 - CloudWatchLogsLogGroup - /aws/eks/{ cluster_name }/cluster - waiting 13:35:15...

@bryantbiggs @antonbabenko I'm marking the PR as a draft because this functionality doesn't work as expected. Terraform doesn't ignore the default Docker image tag at the container definition. In that...

@bolshakoff > Which example can I use to reproduce this? 🤔 I guess it's obvious that I replaced the real names of my project with those values, including the image...

@kaarejoergensen Yes, I think the single option to get an expected result of not tracking `image` tag changes outside of Terraform is to have a separate resource for the ECS...

thanks! However, it will not work for the first ECS task definition and service creation. Only in cases when an appropriate task definition is already present with a pre-defined image...

Hi @remiflament sorry for the late reply > But is it correct that I can use this module if my use case creates a new task_def at each deployment? yes,...

@fextr yes, you're right 👍 using the `data.aws_ecs_container_definition.this.image` leads to a cycle dependency error as this data source requires task definition For example, considering containers can be more than one...

@bryantbiggs @antonbabenko what do you think about this situation? Should we invest in using the `track_latest` ECS task def functionality with the introduction of breaking change? After that, the module's...