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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
Currently the PEM helm chart only supports one way to supply the DB driver jar to the application:
1. Statically provisioned PV bound to the PVC created by the helm chart
A related application, B2Bi, has a helm chart that provides additional options to supply the DB driver jar and other resources to the application:
2. Pre-defined PVC named in values.yaml
e.g. appResourcesPVC.preDefinedResourcePVCName
3. Init Container with included DB jars
https://www.ibm.com/docs/en/b2b-integrator/6.2.0?topic=container-setting-up-init-external-resources
Can these two options be added to the PEM helm chart?
What is your industry? | Non-Industry Specific |
How will this idea be used?
Currently the main ways to handle the resources PVC (containing JDBC driver, etc) are: * Statically provisioned PV bound to the PVC created by the helm chart * Extend the image to include the resources * Fork the helm chart to run our own pre-install steps None of these are particularly great options because: * I want to use dynamically provisioned storage and not worry about creating/deleting PVs * I do not want to extend the image every time a new version comes out * I do not want to update my fork of the helm chart every time a new version comes out Being able to mount an existing PVC lets me use a separate container to populate the PV after it has been dynamically provisioned - without the helm chart deleting and recreating it during the pre-install hook. Attaching an Init Container would accomplish a similar function - populating the resources PV after the pre-install hook creates it dynamically. |
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.