Discussions related to https://github.com/terraform-aws-modules Archive: https://archive.sweetops.com/terraform-aws-modules/
what Adds private_zone option to data lookup. This maintains current behaviour by defaulting to false. why Because sometimes we want to lookup a private hosted zone.
@Chase Ward has joined the channel
Terraform module to provision Auto Scaling Group and Launch Template on AWS - cloudposse/terraform-aws-ec2-autoscale-group
Unfortunately no way to use spot here at the moment either: https://github.com/terraform-aws-modules/terraform-aws-autoscaling/pull/86
Description Convert Autoscaling Group to use Launch Template instead of Launch Configuration Fixes #54 #81 and possibly fixes #44 This is backport from https://github.com/HENNGE/terraform-aws-autos…
No way to use this with spot instances yet, huh?
Their blue ocean controller for kubernetes is far superior
Yeah but for the rest of us plebians still running ASGs, it’d be nice to get those open PR’s merged
oh, sorry! let me have @aknysh take a look
we’ve talked with them and just decided to do it ourselves, but they’ve got a great business model and are doing cool stuff
are you using k8s?
EKS, yes, just starting to kickoff the migration from ECS to EKS and it’ll be slow. We’re using the terraform-aws-modules/terraform-aws-eks with spot instances for most of our workers
The brilliance with blue ocean is it knows (a) how much memory your cluster needs based on requested (b) how much cpu your cluster needs - so it can right size the spot instances in your cluster
but very often, the requested sources are set too high, so spotinst will then recommend how to rightsize your pods
this is why from a UX, we think it’s worth the investment.
(and they have a terraform provider)
(and the node pools are fully managed)