[bitnami/postgresql] Add primary.service.enabled parameter to allow disabling regular service #36431
+16
−4
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 of the change
Adds
primary.service.enabledparameter to allow disabling the regular PostgreSQL primary service. In single-node deployment scenarios, the headless service already provides sufficient functionality for pod discovery, making the regular service optional. This change allows users to disable the regular service when only the headless service is needed, reducing unnecessary Kubernetes resources.The parameter defaults to
trueto maintain backward compatibility - existing deployments will continue to work without any changes.Benefits
trueensures existing deployments are unaffectedPossible drawbacks
None identified. The change is backward compatible and optional.
Applicable issues
Additional information
svc-headless.yaml) remains always enabled as it's required for StatefulSet pod discoveryprimary.service.enabled=false, only the headless service is createdhelm templateto verify both default and disabled scenarios