Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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 Submitted
Created by Guest
Created on Mar 25, 2026

Add native support in the IBM B2B Integrator Helm chart for creating multiple ingress resources with independent ingress classes, hosts, TLS settings, and routing rules.

Many enterprise Kubernetes environments require separate ingress controllers for internal and external traffic—for example, exposing API endpoints publicly while keeping ASI/AC endpoints internal.
The current IBM B2B Integrator Helm chart generates a single ingress resource with a single ingressClass and merges all hosts into it. This prevents the use of different controllers, different TLS certificates, or network segmentation. When additional ingress objects are created manually, they are not Helm‑managed and may be overwritten during upgrades.

The enhancement should allow defining multiple ingress objects directly in values.yaml, each with its own ingressClassName, host definitions, TLS secrets, and path rules.
Supported configuration models could be component‑based (asi/api/ac) or generic (a list of ingress definitions).
This would align the product with common Kubernetes architecture patterns and remove the need for manual post‑installation workarounds.