The 2GB unit for example does not work, one needs to input 2048 as a string (MiB) and it works. Adjusted docs to say this.
removed the 2 task reference in docs, since Kestra currently does not offer more than one task in GCP Batch job
*Note: I don't know if the default is correct in the documentation, as I couldn't find a default set in the code, but it might be a GCP default that is set. Basically this setting of ComputeResources Memory/CPU is required in order to use full power of Batch Runner's compute engine instance. This is because Kestra creates one task for the Compute Engine instance, and you use these settings to set it to use all resources.
How the changes have been QAed?
Ran it in my Kestra instance in 2 scenarios:
default input parameter values for these settings set in workflow
setting input parameter in a different flow that calls the subflow workflow
- id: cpu
type: STRING
defaults: "2000"
description: Defines the amount of CPU resources used by the trask in milliCPU units.
- id: memory
type: STRING
defaults: "4096"
description: Defines the amount of memory used by the task in MiB units.
What changes are being made and why?
The
2GB
unit for example does not work, one needs to input2048
as a string (MiB) and it works. Adjusted docs to say this.removed the 2 task reference in docs, since Kestra currently does not offer more than one task in GCP Batch job
*Note: I don't know if the default is correct in the documentation, as I couldn't find a default set in the code, but it might be a GCP default that is set. Basically this setting of ComputeResources Memory/CPU is required in order to use full power of Batch Runner's compute engine instance. This is because Kestra creates one task for the Compute Engine instance, and you use these settings to set it to use all resources.
How the changes have been QAed?