@@ -19,7 +19,7 @@ A _Pod_ (as in a pod of whales or pea pod) is a group of one or more
|
|||||||
for how to run the containers. A Pod's contents are always co-located and
|
for how to run the containers. A Pod's contents are always co-located and
|
||||||
co-scheduled, and run in a shared context. A Pod models an
|
co-scheduled, and run in a shared context. A Pod models an
|
||||||
application-specific "logical host": it contains one or more application
|
application-specific "logical host": it contains one or more application
|
||||||
containers which are relatively tightly coupled.
|
containers which are relatively tightly coupled.
|
||||||
In non-cloud contexts, applications executed on the same physical or virtual machine are analogous to cloud applications executed on the same logical host.
|
In non-cloud contexts, applications executed on the same physical or virtual machine are analogous to cloud applications executed on the same logical host.
|
||||||
|
|
||||||
As well as application containers, a Pod can contain
|
As well as application containers, a Pod can contain
|
||||||
@@ -51,7 +51,7 @@ with shared namespaces and shared filesystem volumes.
|
|||||||
|
|
||||||
Usually you don't need to create Pods directly, even singleton Pods. Instead, create them using workload resources such as {{< glossary_tooltip text="Deployment"
|
Usually you don't need to create Pods directly, even singleton Pods. Instead, create them using workload resources such as {{< glossary_tooltip text="Deployment"
|
||||||
term_id="deployment" >}} or {{< glossary_tooltip text="Job" term_id="job" >}}.
|
term_id="deployment" >}} or {{< glossary_tooltip text="Job" term_id="job" >}}.
|
||||||
If your Pods need to track state, consider the
|
If your Pods need to track state, consider the
|
||||||
{{< glossary_tooltip text="StatefulSet" term_id="statefulset" >}} resource.
|
{{< glossary_tooltip text="StatefulSet" term_id="statefulset" >}} resource.
|
||||||
|
|
||||||
Pods in a Kubernetes cluster are used in two main ways:
|
Pods in a Kubernetes cluster are used in two main ways:
|
||||||
@@ -65,7 +65,7 @@ Pods in a Kubernetes cluster are used in two main ways:
|
|||||||
tightly coupled and need to share resources. These co-located containers
|
tightly coupled and need to share resources. These co-located containers
|
||||||
form a single cohesive unit of service—for example, one container serving data
|
form a single cohesive unit of service—for example, one container serving data
|
||||||
stored in a shared volume to the public, while a separate _sidecar_ container
|
stored in a shared volume to the public, while a separate _sidecar_ container
|
||||||
refreshes or updates those files.
|
refreshes or updates those files.
|
||||||
The Pod wraps these containers, storage resources, and an ephemeral network
|
The Pod wraps these containers, storage resources, and an ephemeral network
|
||||||
identity together as a single unit.
|
identity together as a single unit.
|
||||||
|
|
||||||
@@ -190,7 +190,7 @@ changing existing code.
|
|||||||
## Resource sharing and communication
|
## Resource sharing and communication
|
||||||
|
|
||||||
Pods enable data sharing and communication among their constituent
|
Pods enable data sharing and communication among their constituent
|
||||||
containters.
|
containers.
|
||||||
|
|
||||||
### Storage in Pods {#pod-storage}
|
### Storage in Pods {#pod-storage}
|
||||||
|
|
||||||
@@ -258,7 +258,7 @@ but cannot be controlled from there.
|
|||||||
configure different Pods with different container runtime configurations.
|
configure different Pods with different container runtime configurations.
|
||||||
* Read about [Pod topology spread constraints](/docs/concepts/workloads/pods/pod-topology-spread-constraints/).
|
* Read about [Pod topology spread constraints](/docs/concepts/workloads/pods/pod-topology-spread-constraints/).
|
||||||
* Read about [PodDisruptionBudget](https://kubernetes.io/docs/concepts/workloads/pods/disruptions/) and how you can use it to manage application availability during disruptions.
|
* Read about [PodDisruptionBudget](https://kubernetes.io/docs/concepts/workloads/pods/disruptions/) and how you can use it to manage application availability during disruptions.
|
||||||
* Pod is a top-level resource in the Kubernetes REST API.
|
* Pod is a top-level resource in the Kubernetes REST API.
|
||||||
The [Pod](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#pod-v1-core)
|
The [Pod](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#pod-v1-core)
|
||||||
object definition describes the object in detail.
|
object definition describes the object in detail.
|
||||||
* [The Distributed System Toolkit: Patterns for Composite Containers](https://kubernetes.io/blog/2015/06/the-distributed-system-toolkit-patterns) explains common layouts for Pods with more than one container.
|
* [The Distributed System Toolkit: Patterns for Composite Containers](https://kubernetes.io/blog/2015/06/the-distributed-system-toolkit-patterns) explains common layouts for Pods with more than one container.
|
||||||
|
|||||||
Reference in New Issue
Block a user