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 Delivered
Workspace API Connect
Created by Guest
Created on Oct 7, 2021

High Availability just for Gateway on CP4I

We have been running API Connect on CP4I on Openshift on Azure cloud since 2019. For an API Connect instance (v10.0.3.0) that is deployed from deployment profile n1xc7.m48, we have been running high availability tests and have noticed that for this profile setting gateways to 3 pods neither provides high availability nor is it supported by IBM. In other words, we require high availability JUST for the Gateway component and not others (such as Analytics, Management Server, Developer Portal). Not having High Availability for the Gateway is a major setback in our Cloud Pak journey whereas going for high availability for all API Connect components is an overkill in terms of licensing and resourcing costs.
Idea priority Urgent
  • Admin
    Dan Temkin
    Mar 31, 2023

    As part of API Connect v10.0.5.2 Updates we have added the a "Medium - Single Replica Profile - Remote Gateway" that will only deploy the Manager, Developer Portal, and Analytics Nodes as single instances and does not deploy any Gateways as part of the 1-Click Platform Navigator install path.

    With this enhancement we have also provided greater documentation around the individual component profiles, CPU limits, memory limits, and licensing for all the pods of a component.

    Once the API Connect components are deployed the Gateway Services can also be deployed on the same cluster or at remote locations following the appropriate steps as described in Installing with subsystems CRs in shared or different namespaces/environments ( This flexibility also allows customers that want to run Gateway in Non-Container deployments (e.g. OVA, Physical, Linux) not to be required to deploy Gateways using the top level CR.

    We also provided a top-level CR for a Large profile with 3 Replicas for the Manager, Portal, and Analytics without a Gateway(s) provisioned.

  • Admin
    Nathan Ziemann
    Nov 11, 2021

    Currently, deploying API Connect through the CP4i platform navigator simplified experience, two static deployment types are available. non-HA, where number of pods is 1 and HA, where pods is 3. Currently there is no way to mix and match HA vs non-HA of different component of the solution. I will accept this as a future candidate.