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 App Connect
Created by Guest
Created on Dec 18, 2024

RELATED IDEAS

increase granularity for control of TCP connections to containers via load balancers

We recently came upon an issue with making a straight TCP connection to a POD in a K8s cluster. This is cluster isn't controlled with OpenShift but it does have the App Connect Operator installed.

We decided to use a cluster load balancer handle the external TCP address and have it connect to the pod where the ACE application was running. However, after opening firewalls and other network pieces we still could not connect to the container in the pod.

We found that the issue was the IntegrationRuntime deployment. It needed the following lines in the spec:

spec:

defaultNetworkPolicy:

enabled: false

So, the fix the issue, we had to disable all the default network policies.

It would be preferable from a user and a security standpoint to have more granularity on these policies to allow users to open certain ports for access while leaving others closed.

Idea priority Medium

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.