DigitalOcean home
  • Droplets
  • Spaces
  • Kubernetes
  • Tools & Integrations
  • One-click Apps
  • API Documentation
  • Community
  • Tutorials
  • Q&A
  • Projects
  • Meetups
  • Customers
  • Pricing
  • Docs
  • Support
  • DigitalOcean home
  • Products
    • Droplets

      Scalable compute services.

    • Spaces

      Simple object storage.

    • Kubernetes

      Run managed Kubernetes clusters.

    • Tools & Integrations

      Automate your infrastructure.

    • One-click Apps

      Deploy pre-built applications.

    • API Documentation
  • Customers
  • Community
    • Community Overview

      Connect, share and learn

    • Tutorials

      DevOps and development guides

    • Questions & Answers

      Development and systems Q&A

    • Projects

      Community-built integrations

    Get Involved
    Write for DOnations
    Join us at a Meetup
    Featured Post
    An Introduction to Kubernetes

    by Justin Ellingwood

  • Pricing
  • Docs
  • Support
    • Documentation

    • Contact Support

    • Network Status

  • Home /
  • DO-I-147 /
  • New idea
27 Vote

Autoscale using saved images when behind a load balancer

You already have alerts and images (snapshots/backups), now all you have to do, is setup some config that when XYZ alert goes off (80% CPU) auto spin up a new droplet (size determined by config) and attach that to the load balancer. This Droplet would start accepting traffic once the health check passes.

As a phase 2, when certain alerts get hit (cpu below 20% for 60 minutes), then de-scale by killing off the youngest droplet.

It seems like all the pieces of the puzzle are there, and it appears that nobody has asked for this specifically like this before on here. Please correct me if I'm wrong.

  • Guest
  • Sep 11 2018
  • Needs review
Autoscaling
  • Comments (4)
  • Votes (27)
  • Attach files
  • Guest commented
    1 Dec, 2020 08:11pm

    This is absolutely needed before we can truly consider running a production site on DO.

    1. Failed servers should be replaced by similar servers (saved images) (MUST HAVE)

    2. If certain load metrics are exceeded, additional servers should be started (REALLY NICE TO HAVE)

    3. The opposite of (2) in order to scale down.

    ×

    Attachments Open full size

  • Guest commented
    31 Dec, 2019 12:54am

    Not just autoscaling, but killing droplets that are malfunctioning and replacing them!! Right now if a Droplet is failing the Load Balancer just stops sending traffic to it and I think we get an alert, but I might be wrong on that since I am just now using DOs load balancer for the first time on a new project.

     

    AWS load balancer is so much nicer because it can autoscale up and down, and destroy an instance if it fails and replace it. Unfortunately aws is too expensive for startups, and people like me prefer DigitalOcean over AWS or Google.

    ×

    Attachments Open full size

  • Guest commented
    11 Sep, 2018 03:46pm

    Minor point: if you killed off the oldest droplet, it would help with configuration drift and other bugs which only manifest in long-running systems.

    ×

    Attachments Open full size

  • Guest commented
    11 Sep, 2018 03:46pm

    This would be really nice for my projects, I could see me using this

    ×

    Attachments Open full size

Log in / Sign up

Identify yourself with your email address

Subscribe

You won't be notified about changes to this idea.

Related ideas

DigitalOcean home

© 2018 DigitalOcean, LLC. All rights reserved.
Proudly made in NY

  • Twitter
  • Facebook
  • Instagram
  • YouTube
  • LinkedIn
  • Glassdoor
Company
About
Leadership
Blog
Careers
Partner Network
Referral Program
Events
Press
Legal & Security
Products
Droplets
Spaces
Kubernetes
Tools & Integrations
One-click Apps
API
Pricing
Documentation
Release Notes
Community
Tutorials
Meetups
Q&A
Write for DOnations
Droplets for Demos
Hatch
Shop Swag
Research Program
Currents Research
Open Source
Support
Contact Support
FAQ
Network Status