IBM Sterling
Hide about this portal


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.

Add a new idea Subscribe
Status Planned for future release
Workspace Sterling B2B Integrator
Categories Installation & Upgrade
Created by Guest
Created on Feb 4, 2025

RELATED IDEAS

dbsetup job should not default to ASI resources

See this idea on ideas.ibm.com

Customer with a large container deployment hit an issue because they have very large requests and limits set for their ASI pods and they could not get the dbsetup job to deploy.


Per the helm chart, it looks like the dbsetup job uses the same requests and limits as ASI, which in most deployments may be fine.

I pasted the section from db-setup-job.yaml below. Formatting is busted but you get the idea.


The best option is probably to make the dbsetup requests and limits settable in the values.yaml with reasonable defaults. I don't think the job resource needs to scale with ASI based on what it is doing.

Another option if you want to keep values.yaml complexity down would be to set the request low with a higher limit so the pod can take whatever is available but won't need a huge node to deploy.

containers: - name: "db-setup" resources: {{- toYaml .Values.asi.resources | nindent 20 }} {{- if .Values.dataSetup.image.digest }} image: "{{ .Values.dataSetup.image.repository }}@{{ .Values.dataSetup.image.digest }}" {{- else }}


What is your industry? Travel & Transportation
How will this idea be used?

Improve container deployment for large customers.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.