[minor] Rds cli image update and create db changes#457
Merged
Conversation
- Update 5 RDS-related Job templates to use new CLI image - New digest: sha256:f211d70d1c6cbc64c073f5ad823f8df7b0bb17f08c9306332eaa11870c4c421c - This image includes pre-installed ibm_db package with libxcrypt-compat - Removes need for runtime installation workarounds in RDS Jobs Files updated: - instance-applications/120-ibm-dbs-rds-database/templates/00-presync-create-database.yaml - instance-applications/120-ibm-dbs-rds-database/templates/01-dbs-rds-postsync-setup.yaml - instance-applications/120-ibm-dbs-rds-database/templates/03-backup-cronjobs.yaml - instance-applications/130-ibm-jdbc-config/templates/00-presync-create-db2-rds-user-Job.yaml - instance-applications/510-550-ibm-mas-suite-app-config/templates/703-postsync-rds-app-roles.yaml
Since CLI base image now includes pre-installed ibm_db and libxcrypt-compat, removed ~230 lines of runtime installation workarounds from 4 RDS Job templates. Changes: - Removed package manager installation attempts (yum/dnf) - Removed RPM download and extraction logic - Removed pip install ibm_db commands - Replaced with simple verification: python3 -c 'import ibm_db' Benefits: - Faster Job execution (30-60 seconds saved) - More reliable (no external dependencies during runtime) - Cleaner, more maintainable code - Consistent with pre-installed dependencies approach Files modified: - instance-applications/120-ibm-dbs-rds-database/templates/00-presync-create-database.yaml - instance-applications/120-ibm-dbs-rds-database/templates/01-dbs-rds-postsync-setup.yaml - instance-applications/130-ibm-jdbc-config/templates/00-presync-create-db2-rds-user-Job.yaml - instance-applications/510-550-ibm-mas-suite-app-config/templates/703-postsync-rds-app-roles.yaml
whitfiea
requested changes
May 14, 2026
Member
whitfiea
left a comment
There was a problem hiding this comment.
these resources need the {{- if .Values.application_admin_role }} around them just like the other resources in the helm charts. application_admin_role would be for application level things like configmaps, jobs in the namespace, whereas cluster_admin_role is for cluster wide resources like clusterissuers
Contributor
Author
|
@whitfiea added the {{- if .Values.application_admin_role }} condition under both files for create database. |
whitfiea
requested changes
May 14, 2026
whitfiea
approved these changes
May 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
Jira:

https://jsw.ibm.com/browse/MASCORE-13709
Argo:

Create DB:

Secret manager got update:
