You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the Postgres operator includes default keys (like HOST) in generated secrets. This causes conflicts when applications use these keys for their own purposes, preventing users from mounting the entire secret without overriding application variables.
Proposed Feature
Add an option to fully override keys in the secret from the secretTemplate, allowing users to drop default keys instead of appending them.
Benefits
Prevents conflicts with application-specific environment variables
Provides greater flexibility in secret configuration
Improves compatibility with various applications
Suggested Implementation
Add a new CRD field, e.g., excludeDefaultKeys that defaults to false
Allow configuring this setting at the operator level
The text was updated successfully, but these errors were encountered:
Description
Currently, the Postgres operator includes default keys (like
HOST
) in generated secrets. This causes conflicts when applications use these keys for their own purposes, preventing users from mounting the entire secret without overriding application variables.Proposed Feature
Add an option to fully override keys in the secret from the
secretTemplate
, allowing users to drop default keys instead of appending them.Benefits
Suggested Implementation
excludeDefaultKeys
that defaults tofalse
The text was updated successfully, but these errors were encountered: