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

Create single reserved instance node for critical pods #13

Open
mattjmcnaughton opened this Issue Nov 28, 2018 · 0 comments

Comments

1 participant
@mattjmcnaughton
Copy link
Owner

mattjmcnaughton commented Nov 28, 2018

Issue
To save money, all of my k8s nodes are spot instances. However, even if I set my maxPrice equal to the on-demand price, there are still windows in which I don't get spot instances. I have critical pods (i.e. online services like my blog) running on these spot instances. In addition, my monitoring/alerting nodes (i.e. prometheus and alertmanager) als run on these spot instances. So I don't even receive alerts when the spot instances are not available.

Impl

  • Purchase a single "reserved instance" node.
  • Create a new kops instance group which will not use spot instances and will use the reserved instance.
  • Use affinities/tolerations to schedule critical pods to this node.

Definition of Done

  • Critical pods are running on a non-spot instance.
  • File ticket to consider if should use spot instance => schedule for 1 month from now.
  • Blog post.

@mattjmcnaughton mattjmcnaughton added this to To do in roadmap Nov 28, 2018

@mattjmcnaughton mattjmcnaughton moved this from To do to In Progress in roadmap Dec 31, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment