To: @Paweł Babilas
CC: @Mykola Marzhan

Hi, I'm jira-bot, Percona's Jira automation tool. I've detected that someone from
Percona has made an edit to the Summary field of an issue that you reported.

I'm not sentient (yet) so I'm not sure whether the person fixed a typo, changed
a few words, or completely rewrote the text. In any case, it is Percona Engineering's
intention to make the Summary and Description of an issue as accurate as possible
so that we're fixing the actual problem you're encountering, and to avoid
misunderstandings about symptoms and causes.

If the current Summary does not accurately reflect the problem you are reporting,
or if you feel the change was otherwise inappropriate in some way, please add a
new comment explaining things and we'll address it as soon as we can.

This message will be added only once per issue, regardless of how many times
the Summary is edited.

message-code:summary-edited

Hi @Paweł Babilas

Thank you for the PR.

Hi, thanks for answear. dunno how i missed this out. PR was send. Thanks

Hi @Paweł Babilas,

once again, we have different sections for different containers in Pod
1. main container - https://github.com/percona/percona-xtradb-cluster-operator/blob/main/deploy/cr.yaml#L76-L86
2. sidecars - https://github.com/percona/percona-xtradb-cluster-operator/blob/main/deploy/cr.yaml#L87-L93
3. log containers - https://github.com/percona/percona-xtradb-cluster-operator/blob/main/deploy/cr.yaml#L352-L355
4. pmm - https://github.com/percona/percona-xtradb-cluster-operator/blob/main/deploy/cr.yaml#L363-L366

if you configured all these sections correctly, without a helm chart - everything should work fine.

could you please show the applied Custom Resource which doesn't work for you?

@Mykola Marzhan,

As you mentioned the limits are available but as I write it sets same resources in every pod container.

this is my configuration for pxc, and it sets for all 4 containers inside pod the same limits so one pod of mysql-pxc has 16 gb limits. Like this: