search

cloud-gov / kubernetes-broker

Broker for kubernetes based services
Apache License 2.0
5 stars 6 forks source link

cpu limits we can actually schedule #41

Closed cnelson closed 7 years ago

cnelson commented 7 years ago

Unlike the docker broker in east which uses cpu shares as relative weights, k8s cpu limits are equal to vCPUs when running on AWS. Since we dropped our vCPU count on minions to 4 in https://github.com/18F/cg-deploy-kubernetes/pull/63 / https://github.com/18F/kubernetes-broker/pull/39 the 6x and 12x jobs cannot be scheduled.

I think we'll want to reduce these to fractions when we do https://github.com/18F/cg-atlas/issues/155 / https://github.com/18F/kubernetes-broker/issues/24 but this at least makes the jobs able to run for now

cc: @brittag @msecret as this also changes the user-facing descriptions you recently updated.

jmcarp commented 7 years ago

Do we need to make the same changes for the other elastic versions?

cnelson commented 7 years ago

I want to remove all other elastic versions from the marketplace as soon as possible as they just make it harder for us to get 5.x so I didn't update them.

I'll add a new story for removing everything but es24 from govcloud if you agree.

On Feb 16, 2017, at 21:46, Joshua Carp notifications@github.com wrote:

Do we need to make the same changes for the other elastic versions?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/18F/kubernetes-broker/pull/41#issuecomment-280559148, or mute the thread https://github.com/notifications/unsubscribe-auth/AAk4Aw9aaDnu_IZ7oW3MUBnwarj8gvzpks5rdTQ5gaJpZM4MD2B3 .