Kubernetes
uses pods to
run an instance of your application. A pod represents a single
instance of your application. Pods typically have a 1:1 mapping with
a container, although there are advanced scenarios where a pod may
contain multiple containers. These multi-container pods are scheduled
together on the same node, and allow containers to share related
resources.
When
you create a pod, you can define resource
requests to
request a certain amount of CPU or memory resources. The Kubernetes
Scheduler tries to schedule the pods to run on a node with available
resources to meet the request. You can also specify maximum resource
limits that prevent a given pod from consuming too much compute
resource from the underlying node. A best practice is to include
resource limits for all pods to help the Kubernetes Scheduler
understand which resources are needed and permitted.
For
more information, see Kubernetes
pods and Kubernetes
pod lifecycle.
A
pod is a logical resource, but the container(s) are where the
application workloads run. Pods are typically ephemeral, disposable
resources, and individually scheduled pods miss some of the high
availability and redundancy features Kubernetes provides. Instead,
pods are usually deployed and managed by Kubernetes Controllers,
such as the Deployment Controller.
0 Response to "Pods"
Post a Comment