Skip to content

Conversation

@itay-grudev
Copy link
Collaborator

This fixes the recovery.pgBaseBackup.secret parameter by correctly setting it as a LocalObjectReference.

I also decided to rename the parameter to: recovery.pgBaseBackup.secretName to better reflect that this is just the secret name.

The non-backwards compatible name change is acceptable here, because the parameter never worked.

Closes: #652 #698

This fixes the `recovery.pgBaseBackup.secret` parameter by correctly setting it as a LocalObjectReference.

I also decided to rename the parameter to: `recovery.pgBaseBackup.secretName` to better reflect that this is just the secret name.

The non-backwards compatible name change is acceptable here, because the parameter never worked.

Signed-off-by: Itay Grudev <itay@verito.digital>
@dosubot dosubot bot added size:S This PR changes 10-29 lines, ignoring generated files. chart( cluster ) Related to the cluster chart labels Nov 24, 2025
@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Dec 4, 2025
@itay-grudev itay-grudev merged commit 565c100 into main Dec 4, 2025
21 checks passed
@itay-grudev itay-grudev deleted the fix/652 branch December 4, 2025 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

chart( cluster ) Related to the cluster chart lgtm This PR has been approved by a maintainer size:S This PR changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Misalignment Between Helm values schema and CRD for pg_basebackup.secret

3 participants