Skip to Main Content
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.


Status Submitted
Created by Guest
Created on Aug 18, 2026

Allow more than one entry in spec.listeners and spec.listeners[].groups so a single EventGateway can advertise both an external and an in-cluster endpoint.

The new EventGateway API 11.8.x (events.ibm.com) is really well structured — modeling spec.listeners and spec.listeners[].groups as arrays with per-group endpoint + advertised-address config is exactly the flexibility we were hoping to leverage. While trying to use it, I have hit a wall where both fields appear to be hard-capped at one item. Adding a second entry to either is rejected by admission with:


The EventGateway "<name>" is invalid: spec.listeners: Too many: 2: must have at most 1 item


The EventGateway "<name>" is invalid: spec.listeners[0].groups: Too many: 2: must have at most 1 item


Since both are arrays, is the single-item cap intentional, and is multi-listener / multi-group support planned? I am trying a use case to advertise two endpoints from one gateway — an external host for remote consumers and an in-cluster host for co-located clients (Event Processing / Flink) — so the latter resolve the gateway natively instead of via /etc/hosts overrides.

Idea priority High