kops: Launching `t3.medium` EC2 instance failed

1. What kops version are you running? The command kops version, will display this information.

Version 1.10.0 (git-782ff1358)

This is branch release-1.10 with #5681 cherry-picked

2. What Kubernetes version are you running? kubectl version will print the version if a cluster is running or provide the Kubernetes version specified as a kops flag.

Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.15", GitCommit:"c2bd642c70b3629223ea3b7db566a267a1e2d0df", GitTreeState:"clean", BuildDate:"2018-07-11T17:59:56Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.11", GitCommit:"b13f2fd682d56eab7a6a2b5a1cab1a3d2c8bdd55", GitTreeState:"clean", BuildDate:"2017-11-25T17:51:39Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

3. What cloud provider are you using?

AWS

4. What commands did you run? What is the simplest way to reproduce this issue?

1. update ig to use t3.medium
2. kops update cluster --yes
3. kops rolling-update --yes

5. What happened after the commands executed?

Node drained, instance terminated but not created, Auto scaling group reported:

Enhanced networking with the Elastic Network Adapter (ENA) is required for the ‘t3.medium’ instance type. Ensure that you are using an AMI that is enabled for ENA. Launching EC2 instance failed.

I’m using the kope.io/k8s-1.8-debian-jessie-amd64-hvm-ebs-2018-03-11 AMI.

Related: #3868

6. What did you expect to happen?

a) kops rolling-update works as normal

b) kops knew t3.medium is not going to work, so refuse to update or rolling-update cluster at first.