Skip to main content

UpdateWorkloadResources

Shows and sets the CPU and memory requests and limits of an adapter or application. Does NOT trigger a deploy — call DeployWorkload afterwards.

Examples​

Shows the current values (also the way to read them for an application):

octo-cli -c UpdateWorkloadResources -id "69cfa838092b710403248acd"

Sets the memory request; the other three values stay as they are:

octo-cli -c UpdateWorkloadResources -id "69cfa838092b710403248acd" -mr "512Mi"

Clears the memory limit (the chart default applies again):

octo-cli -c UpdateWorkloadResources -id "69cfa838092b710403248acd" -ml

Options​

ShortLongRequiredDescription
-id--workloadRtIdyesThe runtime object ID of the adapter or application
-cr--cpu-requestnoCPU request, a Kubernetes quantity such as '250m' or '0.5'. Without a value (or with '') it is cleared
-cl--cpu-limitnoCPU limit, a Kubernetes quantity such as '1' or '1500m'. Without a value (or with '') it is cleared
-mr--memory-requestnoMemory request, a Kubernetes quantity such as '512Mi' or '1Gi'. Without a value (or with '') it is cleared
-ml--memory-limitnoMemory limit, a Kubernetes quantity such as '1Gi' or '3Gi'. Without a value (or with '') it is cleared

Notes​

  • Without any value option the command only shows the current values. An unset value is shown as 'chart default'.

  • An option without a value (or with an empty string) clears that attribute; the other three stay as they are.

  • Quantities and request <= limit are checked here with the same messages the communication controller uses at DeployWorkload; nothing is written when a check fails.

  • The values reach Kubernetes with the next DeployWorkload. Precedence: chart default < these settings < explicit valuesYaml / values[] overrides of the workload; an explicit override wins and the controller reports it in LastDeploymentWarning.

  • Adapter pools are sized with their PoolMember* settings, not with this command.

  • Needs System.Communication 4.10.0 or newer in the tenant.