Skip to content

Conversation

@FxKu
Copy link
Member

@FxKu FxKu commented Nov 5, 2019

If one has configured quite hungry pods in the manifest, one still has to consider it for logical backup pods. There's no way to configure it. By relying only on the default resources it's up to the user to choose adequate requests and limits.

Edit 2023: PR has been updated to provide resource config options for logical backup pod template. When not configured default postgres pod resources will be used. In the future we can also provide manifest fields and use the config options as defaults.

fixes #688

@bchrobot
Copy link

Any update on when this might get merged?

@FxKu
Copy link
Member Author

FxKu commented Jan 16, 2020

I talked with @sdudoladov back when I opened this PR. I think he was more in favor for adding another config parameter. I could also think of taking the resources of the Postgres cluster and dividing them by a configurable factor.

@FxKu FxKu changed the title pass only default resources to logical backup pod configurable resources for logical backup pod template Jan 4, 2023
@FxKu FxKu added the zalando label Jan 4, 2023
@jopadi
Copy link
Member

jopadi commented Jan 5, 2023

👍

1 similar comment
@FxKu
Copy link
Member Author

FxKu commented Jan 5, 2023

👍

@FxKu FxKu merged commit 29cec0c into master Jan 5, 2023
@FxKu FxKu deleted the logical-backup-pod-resources branch January 5, 2023 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Logical backup resource limits

6 participants