Skip to content
AppBahn docs

Your First Deployment

This guide walks you through deploying a Docker container (nginx) to AppBahn. You can follow along using the web console or the CLI.

Prerequisites

Section titled “Prerequisites”
  • An AppBahn instance running on your Kubernetes cluster
  • A workspace, project, and environment already created (see Getting Started)

Step 1: Navigate to Your Environment

Section titled “Step 1: Navigate to Your Environment”

Console

Section titled “Console”
  1. Open the AppBahn console
  2. Select your workspace
  3. Select your project
  4. Select your environment

CLI

Section titled “CLI”
Terminal window
appbahn env list --project your-project-slug

Step 2: Create a Resource

Section titled “Step 2: Create a Resource”

Console

Section titled “Console”
  1. Click + Create Resource
  2. Fill in the form:
    • Name: my-nginx
    • Type: Deployment
    • Image: nginx
    • Tag: 1.27
    • Port: 80
  3. Click Create Resource

CLI

Section titled “CLI”
Terminal window
appbahn resource create \
  --name my-nginx \
  --type deployment \
  --env your-env-slug \
  --image nginx:1.27 \
  --port 80 \
  --expose ingress

Step 3: Watch It Deploy

Section titled “Step 3: Watch It Deploy”

The resource starts in PENDING status. The AppBahn operator creates a Kubernetes Deployment, Service, and Ingress for your container.

Console

Section titled “Console”

The resource list polls automatically. Watch the status badge change from PENDING to READY.

CLI

Section titled “CLI”
Terminal window
appbahn resource get my-nginx-abc12ef

Replace the slug with the one returned from the create command.

Step 4: Trigger a Deployment

Section titled “Step 4: Trigger a Deployment”

To update the running container (e.g., after pushing a new image tag):

Console

Section titled “Console”
  1. Navigate to the resource detail page
  2. Click Deploy

CLI

Section titled “CLI”
Terminal window
appbahn deploy trigger my-nginx-abc12ef

Step 5: Verify

Section titled “Step 5: Verify”

Once the status is READY, the deployment is accessible. If ingress is enabled, visit the domain shown in the resource detail page.

Terminal window
appbahn deploy list my-nginx-abc12ef

What Happens Under the Hood

Section titled “What Happens Under the Hood”
  1. POST /resources validates quotas and license limits, then creates a Kubernetes Custom Resource (CRD)
  2. The AppBahn operator watches for new Resource CRDs
  3. The operator creates a Deployment, Service, and (if expose: ingress) an Ingress
  4. The operator monitors pod health and syncs status back to the platform API
  5. The web console and CLI read the cached status for display

Next Steps

Section titled “Next Steps”