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 updateson 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
When configuring ODF through Satellite, it would be great to have the assignment automatically label the storage nodes correctly so other workloads outside of ODF do not run there.
Today when using Satellite, if you want to setup storage nodes so they are separate from application nodes, you have to perform a config, then assignment, and then you will have to run a script on the cluster to label/taint the nodes correct as described in the RedHat documentation. If you do this step first, then ODF can't deploy, This really causes confusion in the field where Satellite is used to automatically setup ROKS+ODF+Cloud Paks. The assignment should have an option to "do the right thing" if the customer wants to keep ODF and Cloud Paks separate in terms of which worker nodes PODs get deployed into. This should also work correctly if I edit the Satellite config and add new/remove Storage nodes.
Do not place IBM confidential, company confidential, or personal information into any field.