Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Submitted
Created by Guest
Created on Aug 19, 2026

Request for MAS CLI Support for Node Labels, Taints, and Affinity during MAS Installation

I like to request an enhancement to the MAS CLI installation process that allows administrators to specify node placement parameters such as labels, taints, tolerations, and affinity rules during the deployment of a MAS instance.

Many customers use dedicated OpenShift worker pools for specific workloads, applying labels and taints to ensure workload isolation, resource management, security, and compliance requirements. Currently, deploying MAS into a dedicated worker pool may require additional manual configuration after the installation process.

My request is to provide MAS CLI parameters that allow these scheduling constraints to be defined during the execution of mas install, ensuring that all MAS components are deployed directly onto the intended worker pool.

Example of labels:

workload=masdev, environment=nonprod

Node Selector:

workload=masdev

Toleration

key: "workload"

operator: "Equal"

value: "masdev"

effect: "NoSchedule"

This capability would allow customers to deploy MAS instances directly into dedicated worker pools without requiring post-installation modifications, improving operational efficiency and alignment with OpenShift node management best practices.

Idea priority Low
Needed By Not sure -- Just thought it was cool