Skip to Main Content
Integration


This is an IBM Automation portal for Integration 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.

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
Workspace App Connect
Created by Guest
Created on Sep 11, 2024

Add support for tolerations for ACE dashboard.

The CR for ACE dashboard only supports affinity and not tolerations:


https://www.ibm.com/docs/en/app-connect/containers_cd?topic=resources-dashboard-reference


This stops us from locking the dashboard onto specific nodes which are tainted and labelled - because one cannot set the toleration of the taint.



k describe pod ftm-hvp-ace-dashboard-dash-65768cd46b-8cnr2|tail -4


Normal NotTriggerScaleUp 33m (x4 over 53m) cluster-autoscaler pod didn't trigger scale-up: 2 node(s) had untolerated taint {node-role.kubernetes.io/spot: }, 3 node(s) didn't match Pod's node affinity/selector, 2 node(s) had untolerated taint {node-role.kubernetes.io/db2u: }, 2 max node group size reached


Normal NotTriggerScaleUp 28m (x2 over 45m) cluster-autoscaler pod didn't trigger scale-up: 2 node(s) had untolerated taint {node-role.kubernetes.io/db2u: }, 3 node(s) didn't match Pod's node affinity/selector, 2 node(s) had untolerated taint {node-role.kubernetes.io/spot: }, 2 max node group size reached


Normal NotTriggerScaleUp 23m (x15 over 52m) cluster-autoscaler pod didn't trigger scale-up: 3 node(s) didn't match Pod's node affinity/selector, 2 node(s) had untolerated taint {node-role.kubernetes.io/db2u: }, 2 node(s) had untolerated taint {node-role.kubernetes.io/spot: }, 2 max node group size reached


Normal NotTriggerScaleUp 3m9s (x18 over 36m) cluster-autoscaler (combined from similar events): pod didn't trigger scale-up: 2 node(s) had untolerated taint {node-role.kubernetes.io/spot: }, 2 max node group size reached, 2 node(s) had untolerated taint {node-role.kubernetes.io/db2u: }, 3 node(s) didn't match Pod's node affinity/selector

Idea priority Medium
  • Admin
    Ben Thompson
    Reply
    |
    Nov 29, 2024

    Thank you for taking the time to raise this enhancement request. Having introduced support for toleration settings for integration servers and integration runtimes in operator version 9.2.0, we appreciate the value that tolerations can provide so can see some merit in extending support to cover the dashboard. Status updated to Future Consideration.