Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cronjob backup not working with tls #30837

Closed
pthpth opened this issue Dec 9, 2024 · 3 comments
Closed

cronjob backup not working with tls #30837

pthpth opened this issue Dec 9, 2024 · 3 comments
Assignees
Labels
postgresql-ha solved stale 15 days without activity tech-issues The user has a technical issue about an application triage Triage is needed

Comments

@pthpth
Copy link

pthpth commented Dec 9, 2024

Name and Version

bitnami/postgres-ha:15.0.4

What architecture are you using?

amd64

What steps will reproduce the bug?

Running the following helm command

$ helm install mypostgres-ha bitnami/postgresql-ha  -f values.yaml -n postgres-ha
Error: INSTALLATION FAILED: 1 error occurred:
        * CronJob.batch "postgres-ha-postgresql-ha-postgresql-pgdumpall" is invalid: spec.jobTemplate.spec.template.spec.containers[0].volumeMounts[1].name: Not found: "certs"

Are you using any custom parameters or values?

Simplelest new-values.yaml file which creates the error

pgpool:
  tls:
    enabled: true
    autoGenerated: true
posgtres:
  tls:
    enabled: true
    autoGenerated: true
backup:
  enabled: true

What is the expected behavior?

I expect the deployment to be installed.

What do you see instead?

I see the above error message.

Error: INSTALLATION FAILED: 1 error occurred:
        * CronJob.batch "postgres-ha-postgresql-ha-postgresql-pgdumpall" is invalid: spec.jobTemplate.spec.template.spec.containers[0].volumeMounts[1].name: Not found: "certs" 

Additional information

The issue is the same as #20546 which was solved by PR #24468 in postgres charts, the same changes can be made for postgres-ha.

@pthpth pthpth added the tech-issues The user has a technical issue about an application label Dec 9, 2024
@github-actions github-actions bot added the triage Triage is needed label Dec 9, 2024
@carrodher
Copy link
Member

Thank you for opening this issue and submitting the associated Pull Request. Our team will review and provide feedback. Once the PR is merged, the issue will automatically close.

Your contribution is greatly appreciated!

Copy link

This Issue 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. Thanks for the feedback.

@github-actions github-actions bot added the stale 15 days without activity label Dec 27, 2024
Copy link

github-actions bot commented Jan 1, 2025

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

@github-actions github-actions bot added the solved label Jan 1, 2025
@bitnami-bot bitnami-bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
postgresql-ha solved stale 15 days without activity tech-issues The user has a technical issue about an application triage Triage is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants