A job manifest for Runway platform
No Additional PropertiesapiVersion: runway/v1
kind: RunwayJob
metadata:
owner_email_handle: my-username
department: my-dept
department_group: my-dept-group
product_category: my-product-category
spec:
region: us-central1
command:
- /cron
args:
- --arg1
- --arg2
resources:
limits:
cpu: 500m
memory: 128Mi
The API version of the manifest schema
The kind of resource manifest
The email handle of the person or group that owns this job. See https://handbook.gitlab.com/handbook/infrastructure-standards/labels-tags/#owner-email-handle-glowneremail_handle for more information
The department of the person or group that owns this job. See https://handbook.gitlab.com/handbook/infrastructure-standards/labels-tags/#gitlab-department-gl_dept for more information
The department group of the person or group that owns this job. See https://handbook.gitlab.com/handbook/infrastructure-standards/labels-tags/#gitlab-department-group-gldeptgroup for more information
The product category that owns this job. See https://handbook.gitlab.com/handbook/infrastructure-standards/labels-tags/#gitlab-product-category-glproductcategory for more information
The specification of the job
No Additional PropertiesIf the conditions in the "If" tab are respected, then the conditions in the "Then" tab should be respected. Otherwise, the conditions in the "Else" tab should be respected.
The region to run this job in
The command that the container is to start up with. Default is to use the ENTRYPOINT defined in the image
No Additional ItemsArgument you are sending to the container command. If you use multiple arguments, specify each one as a separate item. Default is to use the CMD defined in the image
No Additional ItemsList of sidecar container names that must start before the job container. Only needed when the job container talks to a sidecar during startup. Setting this requires every sidecar to define a startup_probe, since Cloud Run only honors start order when depended-on containers have startup healthchecks.
No Additional ItemsThe container resource management of the service
No Additional PropertiesThe limits to prevent the container from using more than the configured resources. When exceeded, running containers are terminated
No Additional PropertiesThe limit of CPU resources, measured in cpu units
The limit of memory resources, measured in bytes
The amount of memory consumable by the in-memory volume mounted at /scratch, in bytes. Must be less than "memory".
Max allowed time (in seconds) per attempt that the task may be active for before the system will actively try to mark it failed and kill associated containers
Number of retries allowed per task before marking this task as failed.
Schedule configuration for the job
No Additional PropertiesControls if the schedule is paused
Schedule for this job in cron format
VPC connectivity. By default, VPC access is enabled and all egress traffic is routed through the VPC. To use Cloud Run's managed NAT for public endpoints (e.g., Spanner, external APIs), set egress to PRIVATERANGESONLY.
No Additional PropertiesEnable VPC access for connecting to internal services like Memorystore. Defaults to true.
Type of egress traffic that should be routed via the VPC. ALLTRAFFIC routes all outbound requests through the VPC connector (requires proper VPC setup). PRIVATERANGES_ONLY routes only private IP ranges through VPC while using Cloud Run's managed NAT for public endpoints.
List of arbitrary sidecar containers to run alongside the job container. Note: a job task only completes when all containers exit, so long-running sidecars must provide a way to shut down (e.g. an endpoint the job container calls when its work is done).
Must contain a maximum of 5 items
All items must be unique
No Additional ItemsName of the sidecar container. Must be unique within the job. The names "app" and "cloud-sql-proxy-*" are reserved.
^(app$|cloud-sql-proxy-)
^[a-z]([-a-z0-9]*[a-z0-9])?$
Container image for the sidecar.
Entrypoint command for the sidecar container.
No Additional ItemsArguments to pass to the sidecar container.
No Additional ItemsResource management for the sidecar container.
No Additional PropertiesResource limits for the sidecar container.
No Additional PropertiesCPU limit, measured in cpu units.
Memory limit, measured in bytes.
List of container names this sidecar depends on.
No Additional ItemsEnvironment variables for the sidecar container.
No Additional ItemsName of the environment variable.
Plain text value of the environment variable.
Key of a Vault secret synced to GSM for this job.
Path to access on the HTTP server. Mutually exclusive with grpc_service.
Name of the gRPC health status service. Mutually exclusive with path.
Port to probe on the sidecar container.
Value must be strictly greater than 0 and strictly lesser than 65536
Number of seconds after the container has started before the probe is initiated.
Value must be greater or equal to 0 and lesser or equal to 240
Number of seconds after which the probe times out.
Value must be greater or equal to 1 and lesser or equal to 3600
How often (in seconds) to perform the probe.
Value must be greater or equal to 1 and lesser or equal to 240
Minimum consecutive failures for the probe to be considered failed after having succeeded.
Value must be greater or equal to 1
Cloud provider specific configurations
Google Cloud Platform specific configurations
List of connection configuration for CloudSQL instances
Must contain a maximum of 3 items
Connect to CloudSQL instance using a Private Service Connect endpoint
Instance connection name of the CloudSQL instance