Great. Hopefully Azure is next, so we can get ARM Github Actions runners on which I can build ARM binaries. I can already do it with qemu-user but it's slow.
You can already self-host GH Runners on ARM.
Google Kubernetes Engine adds support for Arm nodes
21–30 of 51 posts
Re: Google Kubernetes Engine adds support for Arm nodes
#22Great. Hopefully Azure is next, so we can get ARM Github Actions runners on which I can build ARM binaries. I can already do it with qemu-user but it's slow.
You can already self-host GH Runners on ARM.
The point is to not have to self-host. It costs money, is a pain because maintenance is required, and there are security issues with running CI for public pull requests.
Re: Google Kubernetes Engine adds support for Arm nodes
#23Earlier quoted context omitted.
> you cannot easily source arm hardware commercially Buy Mac Minis and run virtual linux inside?
You can (in theory) run Linux straight on Apple Silicon. It's not locked like the iPad and iPhone. The M1 Ultra would be a pretty solid high volume server if you can manage to plug a 10-40gbps LAN dongle into it. I believe USB-C and/or thunderbolt connectors like that exist. In theory so far because I'm not sure if there are mature installers and such yet.
The Asahi Linux installer worked flawlessly on my MacBook Pro M1 Max, though it asks you to do some low level things like repartitioning the drive.
Re: Google Kubernetes Engine adds support for Arm nodes
#24Looks like it's only available in NA central for now, boooo: https://cloud.google.com/compute/docs/regions-zones#availabl...
Re: Google Kubernetes Engine adds support for Arm nodes
#25It's quite light on details: What properties does the (virtualized) ARM CPU that one gets have? Can it do KVM itself (meaning the underlying real CPU has support for nested KVM)? Can it do ARMv8.3 pointer authentication?
I'd be curious to hear what the use case is for nested KVM. What hardware support is required for that as well?
The instance exposed by GCE is virtualized. If you want to run any hw virtualized workload inside it, you need nested virtualization.
Re: Google Kubernetes Engine adds support for Arm nodes
#26Earlier quoted context omitted.
I am very ignorant of the current ARM cloud offerings. Is it similar prices but less power usage? Or have they had to ramp up the watts to compete?
not sure about pricing here, but graviton on aws has generally offered more performance at a lower price point, which is likely linked to lower power usage and perhaps lower cost of custom silicon vs intel. the notion, "the cloud is expensive", ignores the fact that the cloud is not just rented hardware, but staff, facilities, planning, management, etc.. there are businesses where it makes more sense to own hardware…
> the notion, "the cloud is expensive", ignores the fact that the cloud is not just rented hardware, but staff, facilities, planning, management, etc..
Not at all. Any organization that runs its datacenters can calculate a TCO.
It's really business 101.
Re: Google Kubernetes Engine adds support for Arm nodes
#27Looks like it's only available in NA central for now, boooo: https://cloud.google.com/compute/docs/regions-zones#availabl...
Where did you want it?
Re: Google Kubernetes Engine adds support for Arm nodes
#28Re: Google Kubernetes Engine adds support for Arm nodes
#29Pricing is in line with the cloud: expensive. That's it, they made it: now Arm servers are mainstream.
Dell and HP are still nowhere to be seen in the on-prem Arm server market. Is there not enough of a cost advantage for there to be demand?
Re: Google Kubernetes Engine adds support for Arm nodes
#30Earlier quoted context omitted.
I'd be curious to hear what the use case is for nested KVM. What hardware support is required for that as well?
The instance exposed by GCE is virtualized. If you want to run any hw virtualized workload inside it, you need nested virtualization.
I'd be curious to hear more about your Kubernetes workloads. What virtualized hardware do your pods require?