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 /
  • K8SX-I-40 /
  • New idea
4 Vote

Ability to change nodes size in node pool

Let's say we have some specific nodes for specific tasks. E.g. we deployed Elasticsearch (3 nodes) and assigned Elasticsearch to those nodes with node-pool labels. We grew up and we need more resources for Elasticsearch node pool specifically. Currently, we have to:

Either:

  1. Deploy new node-pool with a different name

  2. Wait for deployment process

  3. Change nodeSelector for Elasticsearch (if it's statefulset, it's even more complicated)

  4. Wait until all pods move to different nodes

  5. Kill old node pool

Or:

  1. Destroy old node pool (downtime guaranteed)

  2. Wait for node pool destruction

  3. Create new node pool with same name, but different resources scale for nodes

  4. Wait for everything to start up

Both processes are either complicated and require a lot of manual work, or have downtime.

It would be better if we could resize node pools by nodes sizes rather than node count only. For example, scale from 4 cores per node to 8 cores per node, with rolling node replacement rather than all-at-once.

  • Igor Boyko
  • Dec 9 2020
  • Needs review
Kubernetes
  • Comments (0)
  • Votes (4)
  • Attach files
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