IBM Cloud - Structured Ideas

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and vote them if they matter to you

  1. Post an idea

  2. Vote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

NOTE: All IBM employees must enter Ideas through this Ideas Portal.

Change Kubernetes worker node machine type in place

This is derived from a GitHub issue for the IBM Cloud terraform provider. The request there is to make it possible to change the machine type of the worker nodes of a Kubernetes cluster.

It is not possible to change the machine type via terraform without destroying the Kubernetes cluster. A new API has to be added for this to be then exposed via terraform as far as I understood.

  • Guest
  • Mar 25 2019
  • Not under consideration
Idea priority High
  • Guest commented
    16 Dec, 2020 04:36pm

    The workaround is fine. At the time of this request, we did not work with worker pools. But in the meantime we do, so that works for us.

  • Admin
    GILLY DEKEL commented
    3 Dec, 2020 02:48pm

    From Sai Vennam :
    "As per the workaround defined by Chris, I wanted to add some details for Terraform. The IBM Cloud Terraform Provider implementation for IKS allows the user to define worker pools. This would allow you to change the worker type without destroying the cluster. User must define their own worker pools instead of simply setting the default worker-type for the default pool."

  • Admin
    GILLY DEKEL commented
    1 Dec, 2020 06:40pm

    From Christopher Rosen:
    "Yes we don't allow this in IKS or ROKS, you need to deploy a new pool and delete the default pool. Status changed to reflect this. "

  • Admin
    CAROL O'Neill commented
    11 Sep, 2020 07:15pm

    Following up to see if you were able to test and resolve?

  • Guest commented
    20 Jun, 2020 06:43am

    It depends on the process of switching worker pools. If I can just change the machine type in the resource definition and the terraform provider automatically creates the new worker pool and then deletes the old one, perfect. I did not test this yet.

  • Guest commented
    17 Jun, 2020 06:39pm

    The correct answer here is to create a new pool and delete the older pool, as the IKS team will not support changing the machine type in place. The flow to switch out worker pools is supported today. Does this satisfy the requirement?

  • Admin
    DAVE TROPEANO commented
    17 Jun, 2020 05:30pm

    reassigned to Sai Vennam

  • Admin
    DAVE TROPEANO commented
    28 Mar, 2019 01:53pm

    Ruben, thank you for the suggestion. The IKS team does feel this is within their scope. As indicated, we are working with you in the GH issue you opened toward a solution path. 

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.