Skip to content

chore: remove unused pgsql configuration from Helm chart values#364

Merged
klesh merged 1 commit intoapache:mainfrom
jeremiahbowen:main
Feb 26, 2026
Merged

chore: remove unused pgsql configuration from Helm chart values#364
klesh merged 1 commit intoapache:mainfrom
jeremiahbowen:main

Conversation

@jeremiahbowen
Copy link
Contributor

Summary

This PR removes the commented pgsql configuration block from the Helm chart values.yaml.

Motivation

The chart currently exposes commented PostgreSQL configuration that appears to suggest PostgreSQL is supported, but:

  • The chart only implements MySQL configuration paths.
  • The pgsql values are not wired into templates.
  • Setting option.database=pgsql does not produce a working deployment.

This creates confusion for users and leads to time spent attempting to configure an unsupported path.

Change

  • Removes the commented pgsql configuration block from values.yaml.
  • Leaves MySQL as the clearly supported database option.

Benefit

  • Reduces ambiguity around supported database backends.
  • Prevents users from attempting a non-functional configuration.
  • Improves chart clarity and maintainability.

If/when PostgreSQL support becomes fully implemented, the configuration can be reintroduced with complete wiring and documentation.

Happy to help reintroduce when full support exists.

### Summary
This PR removes the commented `pgsql` configuration block from the Helm chart `values.yaml`.

### Motivation
The chart currently exposes commented PostgreSQL configuration that appears to suggest PostgreSQL is supported, but:

- The chart only implements MySQL configuration paths.
- The `pgsql` values are not wired into templates.
- Setting `option.database=pgsql` does not produce a working deployment.

This creates confusion for users and leads to time spent attempting to configure an unsupported path.

### Change
- Removes the commented `pgsql` configuration block from values.yaml.
- Leaves MySQL as the clearly supported database option.

### Benefit
- Reduces ambiguity around supported database backends.
- Prevents users from attempting a non-functional configuration.
- Improves chart clarity and maintainability.

If/when PostgreSQL support becomes fully implemented, the configuration can be reintroduced with complete wiring and documentation.

Happy to help reintroduce when full support exists.
@ShankyJS
Copy link

+1

Copy link
Contributor

@klesh klesh left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks for your contribution.

@klesh klesh merged commit 90302c4 into apache:main Feb 26, 2026
3 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants