Fix will come, but it has to bubble up through the stack. I believe your issue is not a memory constraint issue.
But still, you want to increase memory limit:
The manifest feature was merged to edge very recently, and has not been documented yet.
Basically, the following manifest should help you set the memory limit to:
```
software:
mysql-k8s:
config:
profile-limit-memory: 4096
```
N.B: as removal of memory constraint has been merged in edge, if you try to apply this on an old deployment, you would still have the memory constraints in pod definition. You can check that with kubectl describe. You should see NO memory constraints. If some are there, either remove them with an edit, or re-deploy the whole sunbeam
The DPE team has found possible candidate for an issue they have, that is similar to yours:
https:/ /bugs.launchpad .net/juju/ +bug/2052517
Fix will come, but it has to bubble up through the stack. I believe your issue is not a memory constraint issue.
But still, you want to increase memory limit:
The manifest feature was merged to edge very recently, and has not been documented yet.
Basically, the following manifest should help you set the memory limit to: limit-memory: 4096
```
software:
mysql-k8s:
config:
profile-
```
N.B: as removal of memory constraint has been merged in edge, if you try to apply this on an old deployment, you would still have the memory constraints in pod definition. You can check that with kubectl describe. You should see NO memory constraints. If some are there, either remove them with an edit, or re-deploy the whole sunbeam