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
In some case, we need to dedicate some worker nodes to a specific workload.
It can do easily by defining a node selector policy on the namespace and each pods deploy in this namespace will inherited of this policy.
But to work, it's necessary to enable PodNodeSelector admission controller plugin on the Kubernetes ApiServer which is disable on IBM Kubernetes Service.
The workaround is to set the Node Selector policy on each pod, but it is controlled by the application team and not the infrastructure team and it's repetitive. And it can be done through tainted node, but it's really more restrictive than Node Selector.
Please find the kubernetes documentation for the PodNodeSelector admission controller: https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#podnodeselector
Do not place IBM confidential, company confidential, or personal information into any field.