Skip to content
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

Spot price for master #59

Closed
noose opened this issue Jul 6, 2016 · 1 comment
Closed

Spot price for master #59

noose opened this issue Jul 6, 2016 · 1 comment
Labels

Comments

@noose
Copy link

noose commented Jul 6, 2016

Hi!
I know - that's controversial :-) But not everyone are using Kubernetes on production, some of users want to test it, then spot instances should be ok. Imho it must be combined with HA option (for example 3 masters across 3 AZ).
Cheers,
Pawel

@justinsb justinsb added the P2 label Jul 8, 2016
@justinsb
Copy link
Member

justinsb commented Jul 11, 2016

You can now set nodes or masters to use spot instances, using this: https://github.com/kubernetes/kops/blob/master/docs/instance_groups.md#converting-an-instance-group-to-use-spot-instances

I'm not sure that running 3 masters as spot instances is better than just running a single instance as a non-spot instance if availability is the concern. But you can at least do it now!

My fear with spot instances is that in the event an AZ fails, you lose that master. Then everyone else's autoscaling groups put more load into the surviving AZs, and the spot instance price in those AZs goes way up, or spot instances simply become unavailable. In other words that a single AZ failure would result in a failure of 2 or all of your masters. But there isn't a huge amount of data here.

If you try it let us know how it goes - it's definitely useful if you're just testing HA master and want to save some money!

Closing for now, as the feature is implemented. We can continue the discussion though if anyone wants to - it might be that we end up creating a "best practice" document.

rifelpet pushed a commit to rifelpet/kops that referenced this issue Mar 23, 2018
[HBase] Add HBase Master/RegionServer Integration
cloudbow pushed a commit to cloudbow/kops that referenced this issue Jun 8, 2018
…re/upgrade_kafka_to_1 to develop

* commit '2c29f08a4e4c1ec63640917ae02dc48969e67519':
  Fix soccer showing invalid player stats
  Migrate to elastic search hadoop
  Elastic search improvements
  Elastic search improvements
  Upgrade kafka to 1.0.1
  Improve rest layer performance
  Add Test Cases for project
  Add Test Cases for content matcher
  Improvements to logic
  Add cors changes
  QA configuration
  Add rich content for NBA & NCAAB in rest layer
  Add teamstandings for NBA
  Add teamstats for NBA
  Fix scoring events for nba and ncaab
  Add rich metadata for nba, ncaab
  Make spark more reliable
  Update zeppelin to use more memory
  Cleanup code
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants