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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
The current operators for Event Streams and Endpoint Management do support ROKS installation with generation of routes for the default OCP ingress. As we use Service Mesh for all traffic except for mere administration, we'd like to get support of Service Mesh integration for the listed products. We would like to have an option to let the operator create the Gateway and VirtualService definitions with the possibility to adjust major settings such as host names. Also certificates/secrets should be handled by the operator for this scenario.
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.
We are still in conversation to clarify on requiremenmt and urgency, so adding this to pipeline and moving to Future Consideration. Once we conclude the discussion on this, will update it
Please note that the limitations of especially EEM are much worse than I originally thought. For gateway endpoints and most of the EEM endpoints it is not possible to disable route creation. The current operator seems limited to just support a naked default setup to have a single OCP default ingress for all. We have different ALBs and only admin traffic is using the default ingress, all workload is handled via 2 separate ALBs (public and private) bot being managed by ServiceMesh / Istio. This scenario is not just not supported by ES and EEM, it is rather blocked as of today.
To be more precise on that idea. As of now, ES Operator supports creating Routes and Ingress as type for endpoints and listeners but it does not support creating Istio Gateways and Virtual Services. As ServiceMesh Operator is kind of a basic functionality supported by OpenShift, it would be great if the operator could instead of creating just Routes or a custom Ingress/ALB also support creating listeners/endpoints that are integrated into the existing Istio-system setup.
Is it possible that this idea can be made visible for customer vote?