Description:
According to the docs, the configuration of resources for the pitr looks to be in backup.storages.<storage-name>.resources
but adding resources in that location doesn’t make any difference.
The correct location which yields the desired behaviour is actually backup.pitr.resources
, which is not documented.
Version:
1.14
Hello @gmautner
Please report this as documentation bug here https://perconadev.atlassian.net
Thank you.
@gmautner thanks for raising it.
Which doc are you referring to? I was trying to understand it and don’t see us mentioning it anywhere.
The documentation I’m referring to is in the following link:
https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#backupstoragesstorage-nameresourcesrequestsmemory
According to this document, the resources for the pitr pods should be given in the keys backup.storages.STORAGE-NAME.resources.requests.memory
(and similar entries for limits, cpu etc.) inside the spec
key.
However, the key that produces the desired resource allocation is, in reality, spec.backup.pitr.resources.requests.memory
etc. which is not mentioned in the document.
Hi @gmautner, I see your point and I have created task [K8SPXC-1463] - Percona JIRA to fix it. Thank you.