Can't create Mongodb Backup get's stuck in running dued to backup-agent container in PerconaServerMongoDB always crash because of resource limits #838
Description
hi everbody , im currently using everest-operator:1.8.0 in a production workload , the reason behind was moving away from mongodb atlas cause we have some critical applications that runs on pretty old version of mongodb ( version 6 to be precise ) , and atlas is deprecating and auto upgrading all clusters automatically by the end of the month which will be a huge disaster for us . i manged to deploy , configure and migrate the clusters from atlas and everything is working pretty neat so far , the problem start when i try to add some buckups to the clusters created by the everest operator. the backup agent always crash and i figured it is because there's some resource limits apply in the PerconaServerMongoDB that are pretty low , 300m in cpu and 1G of ram , i was digging around and i did not found yet a place to be able to edit or patch those values , when i try to edit the PerconaServerMongoDB resource the changes are not apply , i mean , kubectl say it is ok but if i get the resource again the values are back to the harcoded ones . i assume it has something to do with some webhook that just ignore my changes . and that's it, here i'm stuck with this so i come to you guys if there is some work around in order to be able increase those limits or a "future" plan to change this behavior ?.
i would really aprecciate some help , i've been avoiding to do all this manually because one of the selling points to move from atlas and self manage our clusters with percona + everest was to take advantage of all the features releated with backups ( full and point in time), the ui and kind of have our little dbaas in place like we used to.
thanks in advance .