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 Submitted
Workspace API Connect
Created by Guest
Created on May 8, 2026

RELATED IDEAS

Request for Node Selector and Toleration Support in Nano Gateway to Address Licensing Implications

We have been operating IBM API Connect with the DataPower API Gateway as a component of IBM Cloud Pak for Integration (CP4I) since 2019. We are currently planning a migration to APIC v12.1 utilising the DataPower Nano Gateway (nanogw). However, based on the official documentation and our internal testing, the Nano Gateway follows a serverless architecture in which each deployed Product is instantiated as a separate Pod.

Given that our environment comprises in excess of 100 APIs, this architectural model would necessitate the procurement of a substantial number of VPC licences solely to support the Nano Gateway. By way of illustration, a configuration of 0.3 vCPU per Pod, with 3 Pods per API for high availability across 100 APIs, would require 90 VPCs for the production environment alone. By comparison, the existing DataPower Gateway deployment requires only 9 VPCs to support two environments with high availability.

We believe the resolution to this issue is relatively straightforward: the NanoGatewayCluster custom resource (CR) should be enhanced to support Node Selectors and Tolerations for all Nano Gateway Pods. This would enable the Pods to be constrained to a small number of dedicated OpenShift worker nodes, at which point the IBM License Service would, in all likelihood, cap the reported CPU consumption at the node capacity, irrespective of the aggregate CPU limits defined across the Pods. The IBM License Service may also need to be updated for correct reporting.

This approach is consistent with the methodology we have employed for several years in respect of IBM App Connect Enterprise (ACE) on CP4I, whereby CPU resources are deliberately overcommitted in order to optimize licensing costs.

https://www.ibm.com/docs/en/api-connect/software/12.1.0?topic=licensing-datapower-nano-gateway-deployment-profile-limits

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.