Skip to main content
API resource reference for WorkloadDeployment, part of the Compute service. To create or change one, see Changing resources; to inspect, see Reading resources.
This resource is part of the v1alpha1 API and is subject to change. Fields and behavior may change in future releases.

Identity

Groupcompute.datumapis.com
Versionv1alpha1
KindWorkloadDeployment
ScopeProject

Overview

A WorkloadDeployment represents a single placement of a workload scheduled to a specific location, such as a city. Each deployment belongs to a parent workload (referenced by spec.workloadRef) and corresponds to one of the workload’s placements (spec.placementName). It defines how many instances run through its scale settings and what each instance looks like through its instance template. You typically do not create WorkloadDeployment resources directly — they are produced when a workload is scheduled across its placements. Read them to inspect where a workload has been deployed and how many instances are currently running and ready in a given location.

Spec fields

FieldTypeRequiredDescription
spec.cityCodestringYesThe location target for the deployment; deployments can be scheduled in ways other than just a city code.
spec.placementNamestringYesThe placement in the workload that is driving this deployment.
spec.workloadRefObjectYesThe workload that this deployment belongs to.
spec.workloadRef.namestringYesThe name of the workload.
spec.workloadRef.uidstringYesUID of the workload.
spec.scaleSettingsObjectYesScale settings such as minimum and maximum replica counts.
spec.scaleSettings.instanceManagementPolicystringYesControls how instances are managed during scale up and down, as well as during maintenance events.
spec.scaleSettings.minReplicasintegerYesThe minimum number of replicas.
spec.scaleSettings.maxReplicasintegerNoThe maximum number of replicas.
spec.scaleSettings.metrics[]ObjectNoA list of metrics that determine scaling behavior, such as external metrics.
spec.templateObjectYesDefines settings for each instance.
spec.template.specObjectYesDescribes the desired configuration of an instance (runtime, network interfaces, volumes).
spec.template.metadataObjectNoMetadata of the instances created from this template.

Status fields (read-only)

FieldTypeDescription
status.conditions[]ObjectObservations of the deployment’s current state. Known condition types are Available and Progressing.
status.locationObjectThe location the deployment has been scheduled to.
status.desiredReplicasintegerThe desired number of instances.
status.replicasintegerThe number of instances created.
status.currentReplicasintegerThe number of instances that have the latest workload settings applied.
status.readyReplicasintegerThe number of instances that are ready.

Usage

apiVersion: compute.datumapis.com/v1alpha1
kind: WorkloadDeployment
metadata:
  name: web-us-central
spec:
  cityCode: DFW
  placementName: us-central
  workloadRef:
    name: web
    uid: 4c8f2e1a-9b3d-4f7a-8c21-1e5b7a9d0c3f
  scaleSettings:
    instanceManagementPolicy: RollingUpdate
    minReplicas: 1
    maxReplicas: 3
  template:
    spec:
      runtime: {}
      networkInterfaces:
        - {}
datumctl apply -f workloaddeployment.yaml --project my-project
datumctl get workloaddeployments --project my-project
datumctl describe workloaddeployment web-us-central --project my-project
Run datumctl explain workloaddeployments --recursive to see the full, live field tree for this resource.
Last modified on July 2, 2026