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 Dec 11, 2024

Ability to customize annotations on the ACE IntegrationRuntime deployment resource

We have been running ACE, MQ & API Connect on CP4I LTS release (and now on SC-2) on Openshift on Azure Cloud since 5 years now.

We have a Tekon pipeline that is used to upgrade ACE image (we create our own image from the ACE image in the IBM Entitled Registry) periodically. However each time the image (we use a common imagestream name and tag so that we do not have to modify the image name in Github/ArgoCD apps) is updated, the ACE IntegrationServers/IntegrationRuntimes need to be patched to initiate a new rollout manually.

Ideally on Openshift you could create a Deployment object and tell it to rollout new pod when image or imagestream changes by setting an annotation called "image.openshift.io/triggers", the problem is that the ACE IntegrationServer/IntegrationRuntime does not allow this today, it would be great if this was fixed.

Please ensure that the fix is implemented not just in the CD, but also in the current SC-2 (formerly called LTS) release.

Idea priority Urgent