fix(helm): support preinstalled JDBC drivers#16396
Open
Conversation
Contributor
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
6751ff3 to
3646663
Compare
jgiovaresco
approved these changes
Apr 15, 2026
3646663 to
648440e
Compare
jgiovaresco
approved these changes
Apr 15, 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
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 passedhelm 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-jdbcThis mode disables JDBC runtime provisioning, but does not by itself enforce a read-only filesystem inside the running container