# Upgrade deployment image updates reservations configuration

**URL:** <https://forums.suse.com/t/upgrade-deployment-image-updates-reservations-configuration/16949>\
**Category:** SUSE Rancher Prime\
**Created:** [March 27, 2020, 2:21am UTC](https://forums.suse.com/t/upgrade-deployment-image-updates-reservations-configuration/16949 "2020-03-27T02:21:46Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![thinmy](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/thinmy/32/6208_2.png) [@thinmy](https://forums.suse.com/u/thinmy)\
**Post date:** [March 27, 2020, 2:21am UTC](https://forums.suse.com/t/upgrade-deployment-image-updates-reservations-configuration/16949/1 "2020-03-27T02:21:46Z")

</div>

Hi,

I’m using Rancher v2.3.5 and I realized that when I update a deployment using API (see PUT body below), the deployments CPU and Memory Reservations is updated to default, removing any previous configuration.

body = “{“containers”: [{“name”: “{RANCHER\_WORKLOAD\_NAME}\",\"image\": \"{ECR\_ENDPOINT}:${IMAGE\_VERSION}”}]}”

Any suggestion to resolve this issue?