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

Clarification on K8s Cron backup procedure for Postgres DB #4549

Open
sharpernb opened this issue Sep 23, 2024 · 0 comments
Open

Clarification on K8s Cron backup procedure for Postgres DB #4549

sharpernb opened this issue Sep 23, 2024 · 0 comments
Labels
area:docs Improvements or additions to documentation needs-triage Needs looking at to decide what to do

Comments

@sharpernb
Copy link

sharpernb commented Sep 23, 2024

Description

When configuring the CRON job to execute the pg_dump against Postgres, we encountered an issue where the helm contains an ingress rule that prevents containers from connecting if they don't have app: flowforge as a label.

Error produced:
pg_dump: error: connection to database "flowforge" failed: could not connect to server: Operation timed out
Is the server running on host "flowforge-postgresql.flowforge.svc.cluster.local" (0.0.0.0) and accepting
TCP/IP connections on port 5432?

To Fix:
Added the following to the yaml file for the postgres-backup:

metadata:
  name: postgres-backup
  labels:
    app: flowforge

Following this update we were able to execute the schedule.

@sharpernb sharpernb added the needs-triage Needs looking at to decide what to do label Sep 23, 2024
@hardillb hardillb added the area:docs Improvements or additions to documentation label Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:docs Improvements or additions to documentation needs-triage Needs looking at to decide what to do
Projects
Status: No status
Development

No branches or pull requests

2 participants