Reference
Tactical Edge Compute Node Manager glossary
Terms used in Tactical Edge Compute Node Manager and its documentation.
Applies to Tactical Edge Compute Node Manager as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.
Terms used in Tactical Edge Compute Node Manager and its documentation.
| Term | Meaning |
|---|---|
| Node | A fielded piece of hardware running a Kubernetes cluster or part of one. |
| Update bundle | A signed package of changed images and configuration, split into resumable pieces. |
| Link profile | Expected bandwidth, contact windows and fallback transfer method for a node's links. |
| Contact window | A period when a node expects to have a usable link. |
| Store and forward | Nodes queue reports and pick up waiting updates when a link is available. |
| Baseline | An approved, versioned cluster configuration, including applicable STIG settings. |
| Drift | A change on a node made outside an approved update. |
| Staged rollout | Delivering an update to a first group of nodes before the rest, with health checks in between. |
| Trust anchor | The key material a node uses to check that a bundle was signed by your program. |
| SBOM | Software bill of materials: the list of components in a release. |
Was this page helpful?
Report a problem with this page
Need help with your own setup rather than this page? Raise a support ticket.