spot-instances
Here are 58 public repositories matching this topic...
Currently the Lambda function launches a spot instance, which does version checks for stack, AOSP, Chromium, F-Droid, etc and if there are no new versions will exit. Rather than waste money spinning up an EC2 instance to do this, just run the checks in the Lambda function.
Background:
We run EKS cluster on SPOT instances managed behind an ASG with K8S cluster-autoscaler.
This is pretty obvious use case for SPOTs, lavaraging Kubernetes self-healing and self-regulating features and elasticity provided by ASG.
With around 9-12 instances, we often get intensive SPOT rotation events, where we loose multiple SPOTs within 10-20 mins - sometimes as much as half
-
Updated
Feb 21, 2020 - Python
It would be great to be able to pass through some config to enable metrics where desired. Primarily I was hoping something like this already existed so this module would stop reverting me manually enabling ASG detailed metrics so that I could dashboard them. Passing through at least this option then would be quite helpful https://www.terraform.io/docs/providers/aws/r/autoscaling_group.html#enabled
- add sections / document newly added providers
- document required configuration (env vars)
-
Updated
Feb 13, 2020 - HCL
-
Updated
Feb 15, 2020 - Go
Is this a BUG REPORT or FEATURE REQUEST?:
FEATURE REQUEST
What happened:
k8s-minion-manager can intelligently switch between spot and on-demand instances. However, it doesn't provide information about how much money has been saved because of it. It will be good if the addon can provide that information.
What you expected to happen:
There should be an easy way of seeing the mon
-
Updated
Feb 9, 2020 - Python
-
Updated
Feb 7, 2020 - HCL
-
Updated
Nov 16, 2019 - Go
-
Updated
Jan 17, 2020 - Jupyter Notebook
-
Updated
Dec 19, 2019 - Python
-
Updated
Feb 7, 2020 - Python
-
Updated
Feb 18, 2020 - Java
-
Updated
Feb 16, 2019 - Python
Make a note in the documentation that protected and standby instances are not replaced by spoptimize and execution will stop if the launched instance is detected by spoptimize to be protected from scale-in or is marked as standby.
-
Updated
Sep 18, 2019 - Python
-
Updated
Feb 14, 2020 - Python
-
Updated
Oct 31, 2019 - Shell
-
Updated
Feb 19, 2019 - Shell
-
Updated
Aug 21, 2018 - Python
-
Updated
Jun 29, 2018 - Python
-
Updated
Feb 4, 2019 - JavaScript
-
Updated
Feb 1, 2019 - JavaScript
-
Updated
Feb 22, 2020 - Dockerfile
Improve this page
Add a description, image, and links to the spot-instances topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the spot-instances topic, visit your repo's landing page and select "manage topics."


Issue type
Build number
master branch
Configuration
Deployed as a Stack Set, with a CloudWatch Rule triggering the function
Summary
Can't confirm completely, but I believe the
loggerwhich is created frommain.go'ssetupLoggingfunction does not get created, and therefore