postgresql backup does not provide a NetworkPolicy matching the backup Pod

[axelfauvel]

Name and Version

bitnami/postgresql 14.3.1

What is the problem this feature will solve?

Running postgresql backup on a kubernetes cluster that drops every network communication by default, backup cannot be used without manually creating a NetworkPolicy.

Otherwise, you get this kind of error message :

pg_dumpall: error: connection to server at "postgresql-primary" (172.31.140.138), port 5432 failed: Connection timed out
        Is the server running on that host and accepting TCP/IP connections?

This behaviour differs from primary and read that both comes with their NetworkPolicy.

What is the feature you are proposing to solve the problem?

Add a NetworkPolicy that allows :

• egress: backup -> primary
• ingress: primary <- backup

What alternatives have you considered?

No response

[carrodher]

Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.