- The Kubernetes master is responsible for managing the cluster. All requests to create objects, the scheduling of pods, the managing of
ReplicaSets, and more is happening on the master. The master does not run application workload in a production or production-like cluster. - On each worker node, we have the kubelet, the proxy, and a container runtime.
- The answer is Yes. You cannot run standalone containers on a Kubernetes cluster. Pods are the atomic unit of deployment in such a cluster.
- All containers running inside a pod share the same Linux kernel network namespace. Thus, all processes running inside those containers can communicate with each other through
localhostin a similar way that processes or applications directly running on the host can communicate with each other throughlocalhost. - The
pausecontainer's sole role is to reserve the namespaces of the pod for the containers that run in the pod. - This is a bad idea since all containers of a pod are co-located, which means they run on the same cluster node. But the different component of the application (that is,
web,inventory,anddb) usually have very different requirements in regards to scalability or resource consumption. Thewebcomponent might need to be scaled up and down depending on the traffic and thedbcomponent in turn has special requirements on storage that the others don't have. If we do run every component in its own pod, we are much more flexible in this regard. - We need a mechanism to run multiple instances of a pod in a cluster and make sure that the actual number of pods running always corresponds to the desired number, even when individual pods crash or disappear due to network partition or cluster node failures. The ReplicaSet is this mechanism that provides scalability and self-healing to any application service.
- We need deployment objects whenever we want to update an application service in a Kubernetes cluster without causing downtime to the service. Deployment objects add rolling update and rollback capabilities to ReplicaSets.
- Kubernetes service objects are used to make application services participate in service discovery. They provide a stable endpoint to a set of pods (normally governed by a ReplicaSet or a deployment). Kube services are abstractions which define a logical set of pods and a policy on how to access them. There are four types of Kube services:
- ClusterIP: Exposes the service on an IP address only accessible from inside the cluster; this is a virtual IP (VIP)
- NodePort: Publishes a port in the range 30,000–32767 on every cluster node
- LoadBalancer: This type exposes the application service externally using a cloud provider’s load balancer such as ELB on AWS
- ExternalName: Used when you need to define a proxy for a cluster external service such as a database