Apps & Stacks
Application stacks with container images, resource requirements, and configuration
What you see
URL: /stacks (list), /stacks/[id] (detail)
The Apps & Stacks page lists all application stacks configured in PodWarden, grouped under their parent app. Each stack is a reusable blueprint describing how to run a containerized workload -- the image, resource requirements, environment variables, ports, and volumes. Stacks are deployed to clusters through deployments.
Fields / columns
| Column | Description |
|---|---|
| Name | Display name for the stack |
| Image | Container image name and tag (e.g. ollama/ollama:latest) |
| Kind | Workload type: Deployment, StatefulSet, or DaemonSet |
| CPU | CPU request (e.g. 500m, 2) |
| Memory | Memory request (e.g. 512Mi, 8Gi) |
| GPU | Number of GPUs requested |
| Hub | Shows a badge if this definition was imported from PodWarden Hub |
Available actions
| Action | Where | What it does |
|---|---|---|
| Create | List page toolbar | Opens a blank stack form |
| Import from Hub | List page toolbar | Opens the Hub catalog browser to import a template (requires Hub connection) |
| Import from Compose | List page toolbar | Paste a docker-compose.yml to create a compose stack (see Compose Stacks) |
| Edit | Detail page | Opens the stack form with all fields pre-filled |
| Delete | List page / Detail page | Removes the stack. Fails if active deployments exist |
| View detail | Click a stack row | Opens the stack detail page |
Create stack
The create form lets you configure all aspects of a stack: container image, resource requests (CPU, memory, GPU), environment variables, ports, volumes, and scheduling constraints.
Stack detail page
URL: /stacks/[id]
Click Edit on a detail page to open the stack form with all fields pre-populated. This is the same form as create, but with the existing values filled in.
The detail page shows the full configuration of a stack:
Container
- Image -- Registry URL, image name, and tag
- Command -- Container command override, if set
- Kind -- Deployment type
Resource requests
| Field | Description |
|---|---|
| CPU request | CPU cores or millicores allocated |
| Memory request | RAM allocated |
| GPU count | Number of NVIDIA GPUs |
| VRAM request | GPU memory requirement |
Environment variables
- Static env vars -- Fixed key-value pairs applied to every deployment
- Configurable env vars -- Schema-defined variables with names, defaults, required flags, and descriptions
- Secret references -- References to secrets in PodWarden's encrypted store, injected at deploy time
Ports
A list of container ports to expose, each with a port number and protocol (TCP/UDP).
Volumes
Persistent storage mounts configured for the workload. Supported types include emptyDir, hostPath, PVC, NFS, S3, configMap, and secret.
Scheduling
- Node selector -- Kubernetes label selectors to control placement
- Tolerations -- Tolerations for tainted nodes
- Required network types -- Network connectivity the target cluster must support (
public,mesh,lan)
Security context
- Privileged -- Whether the container runs in privileged mode
- Capabilities -- Linux capabilities added to or dropped from the container (e.g.
NET_ADMIN)
Displayed as badges: red for privileged, amber for added capabilities, gray for dropped capabilities.
Health probes
- Liveness -- Detects stuck containers (Kubernetes restarts them)
- Readiness -- Detects containers not ready to serve traffic
- Startup -- Gives slow-starting containers time to initialize
Displayed as formatted JSON showing probe type (exec, httpGet, tcpSocket) and timing parameters.
Stack type
Every stack shows a type badge:
- Single Service badge -- single container stack (default)
- Compose Stack badge -- multi-service template imported from docker-compose
For Compose Stacks:
- Services list -- shows each compose service name, image, and whether it's the primary service
- Compose source -- collapsible view of the raw
docker-compose.yml
Status badges
| Badge | Meaning |
|---|---|
| Hub | Stack was imported from PodWarden Hub (shows the source template slug) |
| Single Service | Standard single-container stack |
| Compose Stack | Stack has multiple services (imported from docker-compose) |
| Update available | A newer version exists on Hub compared to the imported version |
Related docs
- Deployments -- Deploy stacks to clusters
- Workloads guide -- Detailed guide to creating and configuring stacks
- Settings -- Hub -- Configure Hub connection for imports
- Storage guide -- Volume mount configuration