Common platform terms
| Term | Meaning |
|---|---|
| Workload | A managed object such as a deployment, daemon set or stateful set that owns pods. |
| Readiness | Whether an object is currently able to serve traffic or perform its intended role. |
| Restart growth | An increase in restarts over time, which often matters more than a single historical warning. |
| Namespace boundary | The logical scope that groups objects, policies and ownership into a single operational area. |
| Related object | An owner, node, namespace, service or image that helps explain the current object's behavior. |
| Severity | The impact level attached to an event or signal, such as info, warning or critical. |
Registry and policy terms
| Term | Meaning |
|---|---|
| Image digest | A content-derived image identifier used to distinguish the exact image behind a tag. |
| Immutable tag | A tag that is expected to continue pointing to the same image content. |
| Image consumer | A workload or service that currently references the image. |
| Policy refusal | An intentional denial based on access or endpoint rules rather than a transport failure. |
How to use this glossary
Use the glossary to clear up a term quickly, then return to the operator guides for interpretation and next steps.
ExampleIf a workload is Ready but warnings continue to appear, compare the current readiness state with restart growth before deciding whether the warning stream is operationally important.