Kubernetes Container Terminologies

This guide is intended for users who have basic understanding of containers and container terminologies. This document expects the users to be familiar with the following container terminologies that are used in this guide:

■   Node: A node is a working machine in Kubernetes cluster. They are working units which can be physical, VM, or a cloud instance.
■   Cluster: A group of nodes.
■   Image: Containers are launched from these images (similar to images in cloud environments).
■   Pod: A pod is a collection of containers and its storage inside a node of Kubernetes cluster. It is possible to create a pod with multiple containers inside it.
■   Service: A service is a logical set of pods. It can be defined as an abstraction on the top of the pod which provides a single IP address and DNS name by which pods can be accessed.
■   Namespace: Provides an additional qualification to a resource name. This is helpful when multiple teams are using the same cluster and there is a potential of name collision.
■   Replication controller: Responsible for managing the pod life cycle.
■   DaemonSet: A DaemonSet ensures that all (or some) nodes run a copy of a pod. As nodes are added to the cluster, pods are added to them. As nodes are removed from the cluster, those pods are garbage collected. Deleting a DaemonSet will clean up the pods it created.
■   Job: Main function of a job is to create one or more pod and tracks about the success of pods.

For a detailed list of terms and definitions, refer to the Kubernetes Glossary: https://kubernetes.io/docs/reference/glossary/?fundamental=true