IBM Cloud - Structured Ideas
This portal is to open public enhancement requests against IBM Cloud and its products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
IBM Cloud Support Center (https://cloud.ibm.com/unifiedsupport/cases/form) – Use this site for any IBM Cloud defect or support need.
Stack Overflow (https://stackoverflow.com/questions/tagged/ibm-cloud) – Use this site for IBM Cloud technical Q&A using the tag "ibm-cloud".
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
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.
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."
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. "
Following up to see if you were able to test and resolve?
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.
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?
reassigned to Sai Vennam
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.