Skip to content

fix(helm): support preinstalled JDBC drivers#16396

Open
gutek9 wants to merge 2 commits into4.11.xfrom
fix/add-preinstalled-jdbc-scenario
Open

fix(helm): support preinstalled JDBC drivers#16396
gutek9 wants to merge 2 commits into4.11.xfrom
fix/add-preinstalled-jdbc-scenario

Conversation

@gutek9
Copy link
Copy Markdown
Contributor

@gutek9 gutek9 commented Apr 14, 2026

Description

This PR adds support for a new Helm JDBC delivery mode, jdbc.driverSource=preinstalled, for deployments where the JDBC driver is already baked into the final API and Gateway images.

In this mode, the chart no longer performs JDBC runtime provisioning: it does not create the JDBC initContainer, emptyDir, or plugin directory mount for API, Gateway, or the API upgrader job. The expected behavior is that the JDBC driver is already present in the standard plugin directory inside the custom runtime images.

The PR also updates the Helm documentation and adds regression coverage for the new mode, while preserving the existing behavior for auto, download, and image.

Additionally, it aligns Helm OpenShift security-context adaptation with global values support and applies the same adaptation to the API upgrader JDBC initContainer.

Additional context

Full Helm chart regression was executed with helm unittest -f 'tests/**/*.yaml' .
Result: 116/116 test suites passed, 608/608 tests passed
helm lint . also passed
For jdbc.driverSource=preinstalled, the expected driver locations are:
/opt/graviteeio-management-api/plugins/ext/repository-jdbc
/opt/graviteeio-gateway/plugins/ext/repository-jdbc
This mode disables JDBC runtime provisioning, but does not by itself enforce a read-only filesystem inside the running container

@gutek9 gutek9 requested review from a team as code owners April 14, 2026 14:51
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@gutek9 gutek9 force-pushed the fix/add-preinstalled-jdbc-scenario branch 3 times, most recently from 6751ff3 to 3646663 Compare April 14, 2026 16:07
@gutek9 gutek9 force-pushed the fix/add-preinstalled-jdbc-scenario branch from 3646663 to 648440e Compare April 15, 2026 11:46
@sonarqubecloud
Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants