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 Under review
Workspace API Connect
Created by Guest
Created on Mar 11, 2024

Postgres Images should always use the new Image repository

Currently if the Postgres Crunchy Version is the same between to Fixpacks the old Image Reposiory is still used.


I upgrade from APIC Version to In this to Versions the Crunchy Version is the same.

I have uploaded the Images into to different Image Repositories. E.g. .../apic_10.0.5.4 and .../apic_10.0.5.5

With the Upgrade now all mgmt Pods are using the apic_10.0.5.5 Image Repo (e.g. apim, nats, postgres-operator, ...)

But the 3 Postgres Component

  • postgres

  • pgbouncer

  • postgres-backrest

are still using the .../apic_10.0.5.4 image Repository.

This is ok from a functional aspect ok because the crunchy image is the same in both Versions.

But this leads to some confusions in the Operations Team and also it includes the risk of deleting the old Image Repo, because without knowing this special behavior of the postgres Pods the old repository is not longer needed.

So it would be good to implement a uniform behavior for the Postgres pods as well, so that the Postgres pods also use the new image repository after the upgrade. So that the problems described do not occur any more and the operation of APIC becomes easier.

Idea priority High