Skip to Main Content
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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.

Status Future consideration
Categories Containers
Created by Guest
Created on Oct 21, 2021

Enable PodNodeSelector admission controller plugin

Hello,

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

Regards

Idea priority Medium