Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support of AWS a1.* instances (Arm-based) #6140

Closed
styk-tv opened this issue Dec 1, 2018 · 8 comments · Fixed by #8938
Closed

Support of AWS a1.* instances (Arm-based) #6140

styk-tv opened this issue Dec 1, 2018 · 8 comments · Fixed by #8938
Assignees

Comments

@styk-tv
Copy link

styk-tv commented Dec 1, 2018

With the a1.* instances being significantly cheaper, would it make sense at support of a1.* aws instances?

Type Spec:
https://aws.amazon.com/ec2/instance-types/a1/

@styk-tv styk-tv closed this as completed Dec 1, 2018
@brandon-dacrib
Copy link

This is closed, did this actually happen? Is it inherently there already?

@brandon-dacrib
Copy link

brandon-dacrib commented Dec 6, 2018

It looks like it is in master so we need to wait for a release or do a build yourself.
reference

@dobesv
Copy link

dobesv commented Apr 17, 2019

Just because it was added to the list of instance types that exist doesn't mean anything will work on it. Probably you need an OS image specifically built for ARM and all your docker containers will have to have ARM images.

@apjneeraj
Copy link

It does not work! cloud-init script fails due to exec error. I tried using arm based ubuntu ami.

Aug 1 03:50:04 ip-172-2-96-123 cloud-init[2095]: == Downloaded https://kubeupv2.s3.amazonaws.com/kops/1.12.2/linux/amd64/nodeup (SHA1 = e7e49d1fff61badc2fff402e80858d081aa88a26) ==
Aug 1 03:50:04 ip-172-2-96-123 cloud-init[2095]: Running nodeup
Aug 1 03:50:04 ip-172-2-96-123 cloud-init[2095]: /var/lib/cloud/instance/scripts/part-001: line 133: ./nodeup: cannot execute binary file: Exec format error

@brandon-dacrib
Copy link

That binary is for x86-64. You need to acquire or build one for arm64 and then modify things to pull that. I would start by sorting out what process in the project is building that binary and then submitting a PR modifying that to build for both x86-64 + aarch64.

@hakman
Copy link
Member

hakman commented Apr 6, 2020

M6g, C6g, and R6g have been announced and looks like the performance and value are great.

I will start experimenting with ARM support for Kops. Worker nodes should be pretty easy to configure.

/reopen

@k8s-ci-robot
Copy link
Contributor

@hakman: Reopened this issue.

In response to this:

M6g, C6g, and R6g have been announced and looks like the performance is great:
https://www.anandtech.com/show/15578/cloud-clash-amazon-graviton2-arm-against-intel-and-amd/10

I will start experimenting with ARM support for Kops. Worker nodes should be pretty easy to configure.

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot reopened this Apr 6, 2020
@hakman
Copy link
Member

hakman commented Apr 6, 2020

/assign @hakman

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants