Applications
The App Manager lets you deploy, manage, and schedule containerized workloads on Kubernetes-enabled devices.
Overview
The Applications page has two tabs:
- Applications — deploy and manage apps
- Routines — schedule automated actions (start/stop/restart)
Deploying an Application
1. Select a Target Device
Use the device dropdown to pick a Kubernetes-enabled device. Only devices with Kubernetes installed appear here.
2. Select a Namespace
Choose the Kubernetes namespace to deploy into. Available namespaces are discovered from the target device.
3. Browse the App Catalog
Apps are loaded from configured repositories. Each app has:
- Name and version
- Description
- Tags for filtering
- Configuration fields (API keys, environment variables, etc.)
Use the search bar or tag filter to find apps.
4. Configure and Deploy
Click Deploy on an app to:
- Fill in any required configuration fields (defined in the app's
metadata.yaml) - The server reads the app's Kubernetes manifest template
- Configuration values are substituted (e.g.,
${CONFIG.API_KEY}→ your actual key) - The manifest is applied to the target device via the Kubernetes API
Install vs. Deploy:
- Install — downloads the app but doesn't start it
- Deploy — installs and starts immediately
Managing Deployed Apps
The deployed apps section shows per-device application status with actions:
- Start — start a stopped app
- Stop — stop a running app
- Uninstall — remove the app entirely (with confirmation)
App Repository Structure
Apps are defined in the apps/ directory, each with a metadata.yaml:
name: "my-app"
version: "1.0.0"
description: "My application"
namespace: "default"
config_fields:
- name: "API_KEY"
type: "secret"
description: "API Key for upstream service"
required: true
- name: "LOG_LEVEL"
type: "string"
description: "Log level"
default: "info"
In manifests, placeholders like ${API_KEY} and ${LOG_LEVEL} are replaced with user-provided values.
See App Metadata for the full metadata format and templating behavior.
Adding App Repositories
Use the Repository Manager (gear icon) to add or remove app sources.
Routines
Routines let you schedule recurring actions on deployed apps:
- Action types: Start, Stop, Restart
- Schedule: Cron expression for timing
- Target: Specific apps or tag-based targeting
- Timezone: Configurable per routine
Example: Restart all monitoring apps every night at 2:00 AM.
Permissions
App operations require specific capabilities:
| Action | Required Permission |
|---|---|
| Deploy / Install | apps:deploy |
| Start / Stop / Uninstall | apps:operate |
| Manage repositories | apps:manageRepos |