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
We are currently trying to integrate another container called side car for logging in an integration server. The integration server already consists of one container and we need to add another one. therefore the yaml file should consists of 2 containers. We are not able to achieve same by adding two containers in the yaml file.
Talked with the product team and here's their response: "The CR will not work as it will attempt to run your image instead of the runtime image. We do not currently support side car containers being configured in our CRs. Please raise an RFE for this.".
Idea priority | Low |
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.
Idea review. Thank you for taking the time to raise this suggestion. Unfortunately on this occasion we will not be pursuing this idea further. This is primarily due to our support needs to have a defined position for all behaviours which could be permissible / not permissible within the sidecar without causing problems for the core App Connect container. As an alternate suggestion, we suspect that use of a mutating webhook could help you to achieve your usecase?
Transferring to App Connect.
Is this similar to using our containers with Istio?, as mentioned in this blog article: https://community.ibm.com/community/user/integration/blogs/claudio-tag1/2020/10/30/istio-cp4i-2