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.


Add a new idea Subscribe
Status Future consideration
Workspace API Connect
Created by Guest
Created on Dec 15, 2022

RELATED IDEAS

Ability to configure priorityClassName for all API Connect v10 components

When running API Connect on an Enterprise Kubernetes or OpenShift cluster with multiple applications (and not just IBM API Connect) it is vital that IBM API Connect can run on the cluster and that the kubernetes scheduler can find room for the components.


This can be an issue as IBM API Connect Componentents can often request more CPU than avarage applications running on the cluster. So for example in a patch situation where the cluster nodes are restarted one-by-one there is a chance that the cluster cannot find a node with the required resources as provided in the pod request values.


If this happens it can result in operational instability of IBM API Connect and the cluster as well, since the patching will stop and require manual intervention.


The solution in v2018 was to simply patch the IBM API Connect deployments and stateful sets after installation/upgrade and add spec.priorityClassName to the pods, pointing to a priorityclass that on the cluster was higher than default. This allowed for the cluster scheduler to make sure there was room for the IBM API Connect components on the cluster nodes, moving other pods as needed.


On IBM API Connect v10 it is not possible to provide this configuration through the custom resources. For any of the IBM API Connect components (analytics, manager, portal and gateway). And especially for the API Gateway where request resources are much higher in v10 (they are ENFORCED to be the same as the limit value), this is even more critical and relevant to ensure stable operations on a shared enterprise cluster.


Idea priority Urgent

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.