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 (https://ideas.ibm.com).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
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:
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:
spec:
template:
spec:
tolerations: <our-custom-liberty-node-toleration>
Please see the github registration agreed in a meeting with client and product engineer.
https://github.com/WASdev/websphere-liberty-operator/issues/652
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Hi Kjetil,
IBM WebSphere Liberty team appreciate you taking the time to submit a product idea.
Submitting ideas are an invaluable tool to provide feedback to the product and influence potential future enhancements.
For this reason, the WebSphere Liberty team are happy to inform you that your submitted idea: Add support for tolerations in Liberty Operator has been delivered.
Specifically, your submitted idea was delivered in the product release as follows: 24.0.0.9
You can find more information in our product documentation:
https://www.ibm.com/docs/en/was-liberty/nd?topic=liberty-what-is-new-in-this-release
We would appreciate an update to the submitted idea on how you plan to utilize the product improvement.
Also, you are welcome to submit future ideas to improve or enhance the product based on your usage of WebSphere Liberty.
Additionally, we encourage you to review other submitted ideas by commenting or voting on them.
If you have any questions regarding this update, you can comment on your submitted idea.
Thanks for your interest in our product and directly contributing to its improvement.
Sincerely,
IBM WebSphere Liberty team