Tim Bannister
49eee8fd3d
* Revise Pod concept Adapt the existing Pod documentation to suit the Docsy theme, by promoting the Pod concept itself to /docs/concepts/workloads/pods/ Following on from this, update the Pod Lifecycle page to cover the lifecycle of a Pod and follow on directly from the Pod concept, for readers keen to understand things in detail. This change also removes the automatic contents list from the Pod overview page. Instead, the new page links to all the pages inside the Pod section. * Update links to Pod concept Link to updated content * Incorporate Pod concept suggestions Co-authored-by: Celeste Horgan <celeste@cncf.io> * Revise StatefulSet suggestion for Pod concept Co-authored-by: Celeste Horgan <celeste@cncf.io> Co-authored-by: Celeste Horgan <celeste@cncf.io>
20 lines
617 B
Markdown
Executable File
20 lines
617 B
Markdown
Executable File
---
|
|
title: Pod
|
|
id: pod
|
|
date: 2018-04-12
|
|
full_link: /docs/concepts/workloads/pods/
|
|
short_description: >
|
|
A Pod represents a set of running containers in your cluster.
|
|
|
|
aka:
|
|
tags:
|
|
- core-object
|
|
- fundamental
|
|
---
|
|
The smallest and simplest Kubernetes object. A Pod represents a set of running {{< glossary_tooltip text="containers" term_id="container" >}} on your cluster.
|
|
|
|
<!--more-->
|
|
|
|
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" >}}.
|
|
|