Make postgres initContainer images configurable via values.yaml #116
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.
This PR addresses the hardcoded
postgres:15-alpineimages used in initContainers across multiple Supabase services by making them configurable throughvalues.yaml.Problem
Previously, all initContainers across the Supabase Helm chart used a hardcoded
postgres:15-alpineimage, making it impossible to:Solution
Added a new global
initContainerconfiguration section tovalues.yamlthat follows the same pattern used by other services in the chart:Updated all deployment templates to reference this configurable value instead of the hardcoded image:
charts/supabase/templates/analytics/deployment.yamlcharts/supabase/templates/auth/deployment.yamlcharts/supabase/templates/realtime/deployment.yamlcharts/supabase/templates/storage/deployment.yamlcharts/supabase/templates/test/db.yamlUsage Example
Users can now customize the initContainer image in their
values.yaml:Backward Compatibility
The change is fully backward compatible - the default values maintain the existing behavior (
postgres:15-alpinewithIfNotPresentpull policy).Testing
🤖 This PR was generated by Copilot