Operations
Follow queued, completed and failed app work.
The Operations view shows queued work and operation history, including completed and failed work. Operations are processed by the worker using Helm and Kubernetes and may take time. If work fails, review its reported details and the relevant app and cluster logs before retrying. Verify resulting app and pod status; a submitted operation alone does not confirm that a workload is healthy.
How it works
The API queues an app action so it can run outside the browser request. A worker picks up the operation, invokes the required Helm and Kubernetes work, then records its outcome for the dashboard to display. Queueing separates long-running cluster changes from the UI, but does not guarantee success; inspect the final operation result and resulting workload state.
App requirements and available behavior are defined by the app chart. Review its chart documentation before deploying or changing an app.
Check the result: Use Kubernetes workload status and the relevant chart documentation to verify behavior. Observability views show reported state and do not themselves enforce network or storage boundaries.