Skip to content
This repository has been archived by the owner on Aug 22, 2023. It is now read-only.

Dedicated PostgreSQL role for backups #83

Open
ccremer opened this issue Jun 24, 2022 · 0 comments
Open

Dedicated PostgreSQL role for backups #83

ccremer opened this issue Jun 24, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@ccremer
Copy link
Contributor

ccremer commented Jun 24, 2022

Summary

As service engineer
I want a to create backups with a dedicated backup role in Postgres
So that I can avoid having to use the postgres superuser for backup purposes

This issue should be considered as a technical debt.

Context

In #69 and #80 we engineered backups using K8up so that every database is being backed up.
To that end, a user is required that has access to all databases. At the time, using the superuser postgres was good enough, but raised security concerns in case the user has disabled superuser using the spec.forInstance.enableSuperUser=false flag in the instance spec.

The current implementation has still postgres superuser enabled, even if the user disabled it. The credentials for the superuser are only not exposed in the connection secret, even though connections would technically still work.
This could be an edge case: The user enables superuser, gets or configures the password in an app, disables the superuser again, and the app would still be able to connect.

This issue is about creating and maintaining a Postgres Role that has access to the database and all future databases within an instance.

Out of Scope

  • User-exposed role management
  • Database management

Further links

No response

Acceptance Criteria

No response

Implementation Ideas

No response

@ccremer ccremer added the enhancement New feature or request label Jun 24, 2022
@zugao zugao mentioned this issue Jun 27, 2022
3 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant