An application combines an image, startup parameters, networking, resources, and storage into its desired configuration. Verify the result through replicas, logs, and actual requests.
Decide before creating
| Decision | Why it matters |
|---|---|
| Group and name | The console does not rename applications or move them between groups |
| Persistent data | Local volume mode is chosen during creation |
| Image and startup | Know the listening port, command, and required environment variables |
| Access | Internal communication, published ports, and domains are separate settings |
| Capacity | Each replica and overlapping update tasks need resources |
Readers can inspect shared information. Operators and Admins can create, change, restart, and delete applications. Groups and server resources require an Admin.
Guides by task
Start with creation, images and registries, commands and environment, and resource limits.
Use configuration files for application configuration and persistence for mutable data. Scaling and placement control capacity and location. Updates and restarts and deletion complete the lifecycle.