Skip to Main Content

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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace App Connect
Created by Guest
Created on Dec 9, 2020

Expose deployment strategy on IntegrationServer yaml

We have a scenario where if a container is restarted or re-deployed, the existing container needs to fully terminate before the new container is started. This is the Recreate strategy. The default strategy is RollingUpdate.

A workaround is to update the deployment directly and IFF the integration server is not deleted and recreated, the strategy will survive even after a re-deploy. This is somewhat dangerous if the IS is recreated and the deployment is not also updated.

Idea priority Medium
RFE ID 147296
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Dec 18, 2020

    Thank you for taking the time to raise this request for enhancement and for your direct communications through the service case TS004196739 on this same topic. As noted through these channels, you desire App Connect support for the "Recreate" rolling update strategy (as opposed to the current "RollingUpdate" default) when using ACE in containers on the Redhat OpenShift platform, which in turn requires OpenShift support for Vertical Pod Autoscaling (VPA) for single replicas. A separate enhancement request has been raised against OpenShift for this. ACE development (David Crighton - Ben Thompson and Rob Convery also in the loop) have also been in touch with Red Hat product management (Gaurav Singh) to petition for this change as we see the value here to enable ACE users with usecases like sequencing for example, to be able to run single instance integration servers whilst still benefitting from VPA. The current outlook for the RedHat enhancement being implemented looks very positive, but it is not possible to publicly commit to a delivery timeframe / version at this stage. Status of this RFE is updated to Uncommitted Candidate.