Skip to Main Content
Cloud Platform

This is an IBM Automation portal for Cloud Platform 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Submitted
Workspace WebSphere Liberty
Created by Guest
Created on May 27, 2024

Add support for tolerations in Liberty Operator

Environment: Websphere Liberty on Openshift

We need our Liberty pods to run on dedicated nodes in our clusters and crucially keep all other pods away from these nodes. (The Liberty pods are just a small part of our total number of pods in the cluster).

This would have been very easy to solve with taints and tolerations:

  • Set taint on the dedicated nodes for liberty (this we do ourselves)
  • Set toleration for said taint on the liberty deployments/pods (this we expected to be able to do through the WebsphereLibertyApplication CRD)

Our "workaround" today has been to add a custom-label on all our non-liberty nodes and then set a node-selector on all our "non-liberty-pods" towards that label.

TLDR; it would be more elegant and less maintenance/error-prone for us if we could set tolerations through the WebsphereLibertyApplication CRD. Can this be implemented?

The field within a deployment we would like to manage:

      tolerations: <our-custom-liberty-node-toleration>


Please see the github registration agreed in a meeting with client and product engineer.

Idea priority High