5 ms·
Amazon EKS + Fargate. No bare metal to manage. Control plane complexity is abrastacted away. Fargate namespace + profiles, no worker node configuration. EKS c
by stn_za 4y ago
Amazon EKS + Fargate.
No bare metal to manage.
Control plane complexity is abrastacted away.
Fargate namespace + profiles, no worker node configuration.
EKS cost will be $90/m
Thereafter you only pay for what cpu/mem limits you assign to your deployments/pods.
Otherwise, why bare metal? For your basic needs, bare metal, self managed control planes, etc are definitely over complicating things.
- deleted 4y ago[deleted]
- denvrede 4y agoUsing Fargate for long / permanently running workloads in EKS is only an option when the costs are none of your concern.
- stn_za 4y agoAs opposed to? Fargate is cheap, you can have permanently running workloads and still pay less than non-fargate options.
- easton 4y agoIf you're abstracting away most of the complexity of k8s, why not just go use ECS and spend nothing on the cluster? You will probably have to do some rewriting of your deployment scripts when you move off of EKS anyway (just like when you move off of ECS), so you might as well use ECS and save the $90/m (and it's generally easier to use).