DigitalOcean App Platform Service

Deploys a containerized application on DigitalOcean App Platform as a web service, background worker, or one-off job. The component supports two deployment sources -- building from a git repository or running a pre-built container image from DigitalOcean Container Registry (DOCR). It handles instance sizing, autoscaling, environment variable injection, and optional custom domain configuration backed by a DNS zone reference.

What Gets Created

When you deploy a DigitalOceanAppPlatformService resource, OpenMCF provisions:

• App Platform Application -- a digitalocean_app resource containing a single service component configured according to the chosen serviceType
• Web Service -- created when serviceType is web_service; receives external HTTP traffic, supports autoscaling with CPU-based metrics (80% threshold), and accepts buildCommand/runCommand overrides for git sources
• Worker -- created when serviceType is worker; runs as a background process without HTTP ingress, supports fixed instance counts and environment variables scoped to RUN_TIME
• Job -- created when serviceType is job; executes as a PRE_DEPLOY task, useful for database migrations or one-off scripts
• Custom Domain -- created only when customDomain is specified; adds a PRIMARY domain entry to the app spec and expects DNS to be managed by a referenced DigitalOceanDnsZone resource
• Environment Variables -- injected from the env map; scoped to RUN_AND_BUILD_TIME for web services and RUN_TIME for workers and jobs

Prerequisites

• DigitalOcean credentials configured via environment variables or OpenMCF provider config
• A git repository accessible to DigitalOcean App Platform (for git source deployments), or a DigitalOcean Container Registry with a pushed image (for image source deployments)
• Exactly one source must be provided per deployment: either gitSource or imageSource, never both

Quick Start

Create a file app-service.yaml:

apiVersion: digital-ocean.openmcf.org/v1
kind: DigitalOceanAppPlatformService
metadata:
  name: my-web-app
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: dev.DigitalOceanAppPlatformService.my-web-app
spec:
  serviceName: my-web-app
  region: nyc3
  serviceType: web_service
  gitSource:
    repoUrl: "https://github.com/example/my-app.git"
    branch: main
  instanceSizeSlug: basic-xxs
  instanceCount: 1

Deploy:

openmcf apply -f app-service.yaml

This creates a single-instance web service in the NYC3 region, built from the main branch of the specified git repository using the smallest available instance size.

Configuration Reference

Required Fields

Optional Fields

Examples

Web Service from Git with Custom Build Commands

A Node.js web application built from source with explicit build and run commands:

apiVersion: digital-ocean.openmcf.org/v1
kind: DigitalOceanAppPlatformService
metadata:
  name: node-api
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: dev.DigitalOceanAppPlatformService.node-api
spec:
  serviceName: node-api
  region: fra1
  serviceType: web_service
  gitSource:
    repoUrl: "https://github.com/example/node-api.git"
    branch: main
    buildCommand: "npm ci && npm run build"
    runCommand: "npm start"
  instanceSizeSlug: basic-s
  instanceCount: 2
  env:
    NODE_ENV: "production"
    PORT: "8080"

Worker from Container Registry with Autoscaling Web Service

A background worker deployed from a pre-built container image stored in DigitalOcean Container Registry:

apiVersion: digital-ocean.openmcf.org/v1
kind: DigitalOceanAppPlatformService
metadata:
  name: queue-processor
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: prod.DigitalOceanAppPlatformService.queue-processor
spec:
  serviceName: queue-processor
  region: sfo3
  serviceType: worker
  imageSource:
    registry:
      valueFrom:
        kind: DigitalOceanContainerRegistry
        name: prod-registry
        field: status.outputs.registry_url
    repository: "myapp/queue-processor"
    tag: "v2.1.0"
  instanceSizeSlug: professional-s
  instanceCount: 3
  env:
    REDIS_URL: "redis://private-redis:6379"
    QUEUE_NAME: "tasks"

Production Web Service with Autoscaling and Custom Domain

A fully configured production web service with autoscaling, environment variables, and a custom domain backed by a DNS zone reference:

apiVersion: digital-ocean.openmcf.org/v1
kind: DigitalOceanAppPlatformService
metadata:
  name: prod-frontend
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: prod.DigitalOceanAppPlatformService.prod-frontend
spec:
  serviceName: prod-frontend
  region: ams3
  serviceType: web_service
  imageSource:
    registry:
      valueFrom:
        kind: DigitalOceanContainerRegistry
        name: prod-registry
        field: status.outputs.registry_url
    repository: "myapp/frontend"
    tag: "v3.0.1"
  instanceSizeSlug: professional-m
  enableAutoscale: true
  minInstanceCount: 2
  maxInstanceCount: 10
  env:
    API_BASE_URL: "https://api.example.com"
    LOG_LEVEL: "info"
  customDomain:
    valueFrom:
      kind: DigitalOceanDnsZone
      name: example-zone
      field: spec.domain_name

Stack Outputs

After deployment, the following outputs are available in status.outputs:

Related Components

• DigitalOceanDnsZone -- manages the DNS zone referenced by customDomain for routing traffic to the app
• DigitalOceanContainerRegistry -- hosts private container images used by imageSource deployments
• DigitalOceanDnsRecord -- creates individual DNS records within a zone, useful for additional subdomains pointing to the service
• DigitalOceanFirewall -- controls network access rules for DigitalOcean resources
• DigitalOceanVpc -- provides private networking for other DigitalOcean resources that interact with the app