Open shapirus opened 12 months ago
Hi @shapirus. At the moment it's not possible to use mixed arch. It's been discussed several times, but it's not something easy to add and would require many changes that are not planned at the moment. /kind feature
Hello, is there anything new here please ?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
maybe one day it gets some attention, so let's keep it open.
There's a scalar field to specify the image AMI for an instance group:
.spec.image
However, it is sometimes desirable to run instances of different architectures (arm64 + amd64) in the same instance group, using, for example, the spot mixedInstancesPolicy configuration.
Obviously, this will fail, since all the instance types must match the specified AMI architecture.
Part of the documentation at https://kops.sigs.k8s.io/instance_groups/#spotinstancepools suggests that there might be something of interest:
However I found no further mention of how to configure this Overrides array, which apparently can be used to set AMIs for each specific instance type (as described in https://aws.amazon.com/blogs/compute/supporting-aws-graviton2-and-x86-instance-types-in-the-same-auto-scaling-group/).
Is there any workaround?