Tim Bannister
068f8e4c69
- Mention address family in pod concept Preparing to reword this for IPv4 / IPv6 dual stack - Fix capitalization for “cluster”, “container” and “volume” These are not resources you manage via kubectl - Harmonize short descriptions for workload objects in glossary - Expand definition of StatefulSet - Use tooltip for “kubelet” - Revise pod template text - Revise What's Next section
630 B
Executable File
630 B
Executable File
title, id, date, full_link, short_description, aka, tags
| title | id | date | full_link | short_description | aka | tags | ||
|---|---|---|---|---|---|---|---|---|
| Pod | pod | 2018-04-12 | /docs/concepts/workloads/pods/pod-overview/ | A Pod represents a set of running containers in your cluster. |
|
The smallest and simplest Kubernetes object. A Pod represents a set of running {{< glossary_tooltip text="containers" term_id="container" >}} on your cluster.
A Pod is typically set up to run a single primary container. It can also run optional sidecar containers that add supplementary features like logging. Pods are commonly managed by a {{< glossary_tooltip term_id="deployment" >}}.