Workflows
Purpose
Day-2 link, address, route, doctor, and apply jobs.
How to get there
- Topic id:
workflows - Section: Operations → Workflows
Guide
| Workflow | Steps |
|---|---|
| Lab install | Clone → build → install binary → enable systemd unit (if applicable) |
| Validate | Run status/health command → check logs → confirm metrics or API |
| Upgrade | Stop service → replace binary → migrate config if release notes require → start service |
For netctl-specific examples, see the upstream docs/ tree and tutorials on GitHub.
Operate from the console (UX)
- Open this route from the nav or command palette and wait for live API data.
- Use filters/search when present; drill into a row for detail.
- For mutating actions: confirm role gates and impact before applying.
- Empty / fail: Check service health, auth, and that required CRDs/backends for this domain are installed.
- Success: Live data loads; created/updated objects appear without error toasts.