feat: add external database support and bump chart version to 0.7.0#33
Merged
feat: add external database support and bump chart version to 0.7.0#33
Conversation
vmelikyan
approved these changes
Mar 3, 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 introduces the ability to use an external database (PostgreSQL) for both
lifecycleandkeycloakcomponents. Previously, the system relied solely on internal database containers.With these changes, users can now connect to managed database services (e.g., AWS RDS, Azure Database for PostgreSQL, Cloud SQL) or existing standalone database instances by configuring the
externalDatabaseblock invalues.yaml.🚀 Key Changes
1. External Database Integration
Updated the deployment templates to inject database connection parameters via environment variables when an external DB is enabled:
host,port, anddatabasename.secretKeyRefsupport forAPP_DB_PASSWORD, allowing passwords to be sourced from existing Kubernetes Secrets rather than plain text.APP_DB_HOST,APP_DB_PORT,APP_DB_USER,APP_DB_NAME, andAPP_DB_PASSWORD.2. Configuration Schema (
values.yaml)Added standardized configuration blocks (disabled by default):
externalDatabase.enabled: Toggle to switch between internal and external DB logic.lifecycleandkeycloakincludinghost,port,database,username, andpassword.secretKeyRefstructures.3. Versioning
lifecyclechart version from 0.6.0 to 0.7.0.lifecycle-keycloakdependency alias to version 0.7.0.🛠 Configuration Example
To enable an external database, update your
values.yamlas follows:✅ Checklist
lifecycletemplates.keycloaksub-chart configuration.secretKeyRefmapping for sensitive credentials.values.yamlfor clear documentation.