Skip to content

fix( cluster): Fix incorrect creds for replica templates#806

Open
philippemnoel wants to merge 3 commits intocloudnative-pg:mainfrom
paradedb:phil/azure-recovery
Open

fix( cluster): Fix incorrect creds for replica templates#806
philippemnoel wants to merge 3 commits intocloudnative-pg:mainfrom
paradedb:phil/azure-recovery

Conversation

@philippemnoel
Copy link
Contributor

  • Fix origin-azure-creds.yaml, origin-google-creds.yaml, and origin-s3-creds.yaml templates that read from .Values.recovery.* instead of .Values.replica.origin.objectStore.*

These templates are gated on mode == "replica" but were reading credential values and secret names from the recovery values tree. This is a copy-paste bug from the recovery-*-creds.yaml templates — the conditions were updated but the data fields were not. In replica mode, the recovery.* values are empty, so the generated secrets would contain blank credentials.

For reference, origin-s3-creds.yaml already had the correct paths for the S3 access/secret key data fields and the required error messages, but the secret name was still reading from .Values.recovery.secret.name.

@dosubot dosubot bot added size:M This PR changes 30-99 lines, ignoring generated files. bug Something isn't working chart( cluster ) Related to the cluster chart labels Feb 9, 2026
Signed-off-by: Philippe Noël <[email protected]>
Signed-off-by: Philippe Noël <[email protected]>
Signed-off-by: Philippe Noël <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working chart( cluster ) Related to the cluster chart size:M This PR changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant