Workloads
1. Overview
The Workloads screen shows, in a single place, everything that's deployed on the platform — Flows, Apps, and Add-ons — and which environment each one is running in. It's the central place to see what currently exists in production/test, and to remove a deployment directly from the table, without having to navigate to each resource's origin screen.
2. Filters
| Filter | Description |
|---|---|
| Squad | Squad that owns the displayed workloads. |
| Environment | Restricts the list to a specific environment. |
3. Workloads Table
| Column | Description |
|---|---|
| Workload | Name of the deployed workload (e.g. nukk-site). |
| Squad | Squad that owns the workload. |
| Container Memory | Memory allocated to the container (e.g. 512MB). |
| Replicas | Number of replicas running. |
| Environment | Environment the workload is running in (e.g. Test). |
| Last Update | Date/time of the workload's last update. |
| Status | Current state (e.g. DEPLOYED). |
| Actions | Actions available for the workload, including removing the deployment (trash icon). |
Clicking the trash icon under Actions removes that workload's deployment from the selected environment.
4. FAQ
Does removing a workload here delete its data (database, files, etc)? Every app runs as stateless — no volume is configured for it. When the workload is removed, the pod is removed from the infrastructure, and there's no persistent data belonging to that app to be deleted.
Can a removed workload be redeployed without redoing the whole configuration? Yes. Just select the Flow or App you want to redeploy, choose the configuration, and deploy it again.