Skip to content
This repository has been archived by the owner on Sep 30, 2020. It is now read-only.

kube-aws caculator does not recognize t2.xlarge type #388

Closed
andromedarabbit opened this issue Mar 7, 2017 · 4 comments
Closed

kube-aws caculator does not recognize t2.xlarge type #388

andromedarabbit opened this issue Mar 7, 2017 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@andromedarabbit
Copy link
Contributor

Error: failed to estimate cost for node pool #0 ValidationError: t2.xlarge is an invalid InstanceType value. Valid values are [c1.medium, c1.xlarge, c3.2xlarge, c3.4xlarge, c3.8xlarge, c3.large, c3.xlarge, c4.2xlarge, c4.4xlarge, c4.8xlarge, c4.large, c4.xlarge, cc1.4xlarge, cc2.8xlarge, cg1.4xlarge, cr1.8xlarge, d2.2xlarge, d2.4xlarge, d2.8xlarge, d2.xlarge, g2.2xlarge, g2.8xlarge, hi1.4xlarge, hs1.8xlarge, i2.2xlarge, i2.4xlarge, i2.8xlarge, i2.xlarge, m1.large, m1.medium, m1.small, m1.xlarge, m2.2xlarge, m2.4xlarge, m2.xlarge, m3.2xlarge, m3.large, m3.medium, m3.xlarge, m4.10xlarge, m4.2xlarge, m4.4xlarge, m4.large, m4.xlarge, r3.2xlarge, r3.4xlarge, r3.8xlarge, r3.large, r3.xlarge, t1.micro, t2.large, t2.medium, t2.micro, t2.small]

New instance type is not recognized
@mumoshu
Copy link
Contributor

mumoshu commented Mar 10, 2017

Thanks for the report @andromedarabbit!
@gianrubio Any chance you could look into this? Perhaps we'd need to upgrade our aws-sdk-go to catch up with latest instance types or is it just a cloudformation restriction?

@mumoshu mumoshu added the kind/bug Categorizes issue or PR as related to a bug. label Mar 10, 2017
@gianrubio
Copy link
Contributor

Yes @mumoshu, I'll do that during this weekend

@gianrubio gianrubio mentioned this issue Mar 12, 2017
Merged
@gianrubio
Copy link
Contributor

@mumoshu upgrading the aws-sdk-go fix this error

gianrubio added a commit to gianrubio/kube-aws that referenced this issue Mar 12, 2017
@gianrubio
upgrade aws-sdk to latest version
4f9858e 
Fix kubernetes-retired#388
@andromedarabbit
Copy link
Contributor Author

I appreciate that.

camilb added a commit to camilb/kube-aws that referenced this issue Apr 5, 2017
@camilb
Merge remote-tracking branch 'kubernetes-incubator/master'
7f93c09 
* kubernetes-incubator/master: (29 commits)
  Emit errors when kube-aws sees unexpected keys in cluster.yaml Resolves kubernetes-retired#404
  Tag controller nodes appropriately with `kubernetes.io/role`. Resolves kubernetes-retired#370
  Make Container Linux AMI fetching a bit more reliable
  Stop locksmithd errors on etcd nodes
  Upgrade heapster to version 1.3.0 (kubernetes-retired#420)
  Auth token file support (kubernetes-retired#418)
  Update README.md
  Update README accordingly to the new git repo
  AWS China region support (kubernetes-retired#390)
  Conform as a Kubernetes Incubator Project
  Fixed typo in template
  upgrade aws-sdk to latest version Fix kubernetes-retired#388
  Upgrade Kubernetes version to v1.5.4
  Fix assumed public hostnames for EC2 instances in us-east-1
  Fix assumed public hostnames for EC2 instances in us-east-1
  typo
  fix: etcdDataVolumeEncrypted not creating encrypted volumes fixes kubernetes-retired#383
  Allow disabling wait signals fixes kubernetes-retired#371
  Update file paths in readme
  Fix an issue with glue security group documentation
  ...
kylehodgetts pushed a commit to HotelsDotCom/kube-aws that referenced this issue Mar 27, 2018
@gianrubio
upgrade aws-sdk to latest version
481b4a6 
Fix kubernetes-retired#388
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mumoshu @andromedarabbit @gianrubio