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 Delivered
Workspace API Connect
Created by Guest
Created on Apr 6, 2022

RELATED IDEAS

Limit CPU Consumption of API Connect componentes in Kubernetes Clusters to stay below purchased licenses

We use API Connect (including API Gateway) components in Kubernetes Clusters. we have purchased a certain amount of licenses (VPCs/PVUs). Currently there is no way to definie API Connect deployments to use no more CPUs than defined (for example: number of licenses purchased). There is only a possibility to define deployment profiles which will define the mimnimum number of CPUs.


Limiting the size (CPUs) of worker nodes to match the maximum number of CPUs used for API Connect is not a proper option, as

  • additional, non-API Connect traffic may also be running inside the same cluster

  • benefits of cluster deployments, like failover of pods to other worker nodes in case of an outage of a worker node, can not take effect.

We need a solution that gives IBM and us the guaranty that we stay within licensing limits and at the same lets us enjoy the benefit and flexibility of kubernetes deployments

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.