-
Notifications
You must be signed in to change notification settings - Fork 467
kube-aws: Node pools #667
Comments
@mumoshu to clarify- are you talking about having multiple specifications for worker nodes? workers:
- instanceType: m3.medium
count: 4
labels:
....
- instanceType: t2.small
count: 20
labels:
.... |
@colhom Yes. It would also be good to have
so that we can also provide a way to solve #668 |
I'm starting to migrate our docker containers to kubernetes, and would like most of our services to run on fairly small machines (m3.medium, 3.75 GB Memory), but a few of our containers require lots of memory (16 GB each). It would be fantastic if it was possible to run a cluster with mixed instance types, such that the lightweight containers could live on the small instances, and the big containers could live on the big instances. I know that it's possible to make the containers prefer specific nodes using the labels, I just need to be able to run the bigger instances as part of the cluster. |
I'm thinking of how I could build a POC of this. I'd like to have something consistent with today's For the time being, I've come up with something like:
...which is heavily inspired by the node-pools feature and its related Any thoughts, suggestions, etc? |
Closing, as I'd like to discuss further in the new repo 💨 |
I'd like to add GKE's "Node Pools" like feature on top of kube-aws so that, without maintaining multiple etcd clusters and kubernetes controller planes, mainly for cost optimization purpose:
(1) I can differentiate
for each node pool
(2) Make a node pool a spot fleet
Do you think it would be appropriate to implement it in
kube-aws
or in another repo?cc @colhom
The text was updated successfully, but these errors were encountered: