aws-helm-multi-deploy VS keel

To help you deploy these, your CI/CD framework or tooling needs to run helm dependencies update before it does a helm diff/update. Here's an Github Action which does this in an opinionated fashion

I think you're talking about two different things. I personally recommend hard boundaries of what your tools do. For IaC, do IaC. For services, use CI/CD. So, for all my clients, I stand up infrastructures with Terraform except for EKS, which I use EKSCTL. These tools are run very rarely, only when you need to adjust/alter/upgrade your infrastructure, but NOT your services. After Kubernetes is stood up though, managing it with Terraform is terrible. Simply use Helm via your CI/CD toolchain. Here's an Github Action my team engineered to deploy via helm recursively easily: https://github.com/DevOps-Nirvana/aws-helm-multi-deploy

I just want to throw in keel as another alternative.

There are multiple tools available for that. Another one could be https://keel.sh

Flux for Kubernetes and we have installed Keel to let devs restart deployments on Development cluster. We don't use Webhooks but just have them do Powershell request to endpoint either in their pipeline or manually depending on dev teams desire.

Have you seen keel? https://github.com/keel-hq/keel I'm using it on very small projects with very simple delivery logic, so I'm not sure if it's gonna work out in your case, you can give it a try though.

There is also a 3rd party tool like Keel but it doesn't support Amazon ECR (Webhook problem with ECR).

This got a little off track... I don't have a problem. You have a problem! but TLDR; keel?

I’ve used keel to help me with this issue: https://keel.sh.

Keel might be of interest.

I've used Keel and more recently ArgoCD Image Updater (Using ArgoCD to manage deployments).