atomic unit of scheduling
all container in pod share the pod environment. anything attached to pod, all container can use it.
it can contain one or more containers.
pod can have tight coupling- loose coupling.
pods are atomic, you can scale the port from 1 to many.
pods are the application which can access through n/w.
pods contain container. and runs as long as container run.
multi container pods – main container and side car container.
pod lifecycle: phase: pending –> phase: running –> phase: succeeded/failed.
inter pod communication : using pod n/w (created by kube-proxy).
intra pod communication: through localhost
no pod is ever redeployed
unit of scheduling
remote access: using pod IP address and pod port number(multi container).