Skip to content

[bitnami/postgresql] Add primary.service.enabled parameter to allow disabling regular service#36431

Merged
fmulero merged 4 commits intobitnami:mainfrom
aravind4799:add-primary-service-enabled
Feb 9, 2026
Merged

[bitnami/postgresql] Add primary.service.enabled parameter to allow disabling regular service#36431
fmulero merged 4 commits intobitnami:mainfrom
aravind4799:add-primary-service-enabled

Conversation

@aravind4799
Copy link
Copy Markdown
Contributor

@aravind4799 aravind4799 commented Jan 11, 2026

Description of the change

Adds primary.service.enabled parameter 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 true to maintain backward compatibility - existing deployments will continue to work without any changes.

Benefits

  • Reduced resource overhead: Users can disable the regular service in single-node deployments where only the headless service is needed
  • More flexible configuration: Provides users with control over which services are created
  • Backward compatible: Default value of true ensures existing deployments are unaffected

Possible drawbacks

None identified. The change is backward compatible and optional.

Applicable issues

Additional information

  • The headless service (svc-headless.yaml) remains always enabled as it's required for StatefulSet pod discovery
  • When primary.service.enabled=false, only the headless service is created
  • Tested with helm template to verify both default and disabled scenarios

…isabling regular service

Signed-off-by: aravind <araviku04@gmail.com>
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
@carrodher carrodher added verify Execute verification workflow for these changes in-progress labels Jan 12, 2026
@github-actions github-actions bot removed the triage Triage is needed label Jan 12, 2026
@github-actions github-actions bot removed the request for review from carrodher January 12, 2026 08:01
@github-actions github-actions bot requested a review from fmulero January 12, 2026 08:01
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
@github-actions
Copy link
Copy Markdown

This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.

@github-actions github-actions bot added the stale 15 days without activity label Jan 28, 2026
@aravind4799
Copy link
Copy Markdown
Contributor Author

Let me know if there are any chances

@github-actions github-actions bot removed the stale 15 days without activity label Jan 29, 2026
Copy link
Copy Markdown
Collaborator

@fmulero fmulero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thnaks a lot @aravind4799 for your contribution and Sorry about my very late response.

LGTM

@fmulero fmulero merged commit b631836 into bitnami:main Feb 9, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

postgresql solved verify Execute verification workflow for these changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

add service.enabled helm value

4 participants