Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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.

Created by Guest
Created on May 22, 2026

Helm Charts Version 3.2.0 for IBM Sterling File Gateway missing resource limits

I am deploying Helm Charts Version 3.2.0 for IBM Sterling File Gateway Enterprise Edition v6.2.2.0.

Openshift teams commonly enforce resource limits on every pod that is being created. During the course of deploying version 3.2.0 of the SFG chart, I found the following containers do not have resource min/max

File - ibm-sfg-prod\templates\db-setup-job.yaml
name: "resources-init"

File - ibm-sfg-prod\templates\asi-statefulset.yaml
name: "resources-init"

File - ibm-sfg-prod\templates\asi-statefulset.yaml
name: "customization-init"

This is causing the helm chart to be rejected. I manually added the resources min/max to those containers to resolve the issue. Otherwise we would not be able to deploy the application. This is a very common requirement from Openshift teams, and I would appreciate the support on this enhancement on all Sterling App Helm Charts.

 

I opened a support case to see if the changes to the helm chart would be supported and this is the response I got:

If a customer wants to enforce resource requests/limits, he or she can add "resources:" block directly to the resources-init definition in asi-statefulset.yaml template. From a Kubernetes standpoint, this will work.

 

While the above is technically feasible, for IBM SFG 6.2.2.0 Certified Containers, this is NOT supported by IBM, because:

 

- asi-statefulset.yaml is an IBM?delivered Helm template

- Editing it is considered chart modification

- IBM support treats this as a custom fork

- Changes are overwritten on upgrade / fix pack

- IBM may decline support if issues arise

 

If you still want to make this available in SFG helm chart template files and then in values.yaml file, please consider submitting an enhancement request on this IBM website (please select product "Sterling B2B Integrator" ) :

 

https://ideas.ibm.com/new-idea

  • Admin
    James Joseph
    Aug 12, 2026

    The following are the SFG container components do not have resource min/max limits available to configure.

    File - ibm-sfg-prod\templates\db-setup-job.yaml

    name: "resources-init"

    File - ibm-sfg-prod\templates\asi-statefulset.yaml

    name: "resources-init"

    File - ibm-sfg-prod\templates\asi-statefulset.yaml

    name: "customization-init"

    File - ibm-sfg-prod\templates\api-statefulset.yaml

    name: "resources-init"

    File - ibm-sfg-prod\templates\api-statefulset.yaml

    name: "customization-init"

    File - ibm-sfg-prod\templates\ac-statefulset.yaml

    name: "resources-init"

    File - ibm-sfg-prod\templates\ac-statefulset.yaml

    name: "customization-init"

    File - ibm-sfg-prod\templates\ext-purge-job.yaml
    name: "resources-init"

  • Guest
    Aug 11, 2026

    Hi James,

    This enhancement was originally raised for resourcesInit, customizationInit, and dbsetup. The dbsetup component has already been addressed in the 6.2.2.1 release. However, rather than handling these capabilities on a component-by-component basis, I would like to generalize this requirement and establish it as a standard across the platform.

    Any service or component deployed as a pod should provide configurable resource allocations, including CPU and memory requests/limits (minimum and maximum values). These settings should be shipped with sensible default values while allowing customers to adjust them based on their deployment requirements and operational needs. This would ensure consistency across all components, whether it is Document Service, ITX integration, AS4 Microservice, or any future pod-based service for providing greater deployment flexibility.

    Thanks,

    Rama.

  • Admin
    James Joseph
    Jul 22, 2026

    We are accepting the idea and considering it future releases. we can revisit this once we see the traction from other customers and partners (via Voting or Comments). Thank you for your patience and co-operation.

    Thanks,

    James

  • Admin
    James Joseph
    Jun 10, 2026

    Thank you for taking the time to share your ideas to IBM. We truly value our relationship with you and appreciate your efforts and willingness to share details about your experience, your recommendations, and ideas. We will soon review the same in the coming weeks and shall get back with a response.
    Thanks,

    James

  • Guest
    May 22, 2026

    Great idea!!