Possibility of using different aws-node-termination-handler version

[ridzuan5757]

I stumbled upon this problem where the aws-node-termination-handler stuch in CrashLoopBackOff state when deploying in ap-southeast-5 region as described in this issue:
aws/aws-node-termination-handler#1069

Is it possible to use different version for this container when kops is creating a new cluster?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale