CLI should warn users about limitation of using the new AWS instance types (P3, C5, M5, H1)

[sidguptajhs]

Q & A

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

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.
   1.8.5

3. What cloud provider are you using?
   AWS

4. What commands did you run? What is the simplest way to reproduce this issue?
   helm install --name mongo stable/mongodb-replicaset

5. What happened after the commands executed?
   The storage controller fails to mount persistent volumes when using P3/C5/M5/H1 instances.

6. What did you expect to happen?
   This is unexpected for someone who did not read the KOPS release notes about the NVME limitation in Kubernetes 1.8

REQUESTED CHANGE:

1. Describe IN DETAIL the feature/behavior/change you would like to see.
   Some warning in the CLI, or better error logging in the storage controller for AWS.

[erickt]

I think this is a dup of #3868.

[blakebarnett]

#3868 is about supporting them, this is about warning users they are not suitable for use currently. I think we should warn until the stability of the instance types is improved.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close