Glossar

NameDescription
NodeA machine on which Kubernetes runs (either a physical or virtual server).

Master / Control Plane:
The master nodes are responsible for managing the Kubernetes control plane. They coordinate the cluster, provide the Kubernetes API, and handle all core management tasks.

Worker Nodes:
The worker nodes run the deployed applications and their associated resources.
ClusterA cluster is a group of nodes that work together to provide high availability and fault tolerance in case one node fails.
NamespaceA namespace is like a project in Kubernetes. Different namespaces are isolated from each other at the network level but can communicate if explicitly allowed (similar to a firewall rule). It serves as a logical grouping for applications and resources.
Service (Networking)A Service is a networking component that allows different Pods to communicate with each other and with the outside world. You can define input and output ports, as well as the communication protocol.
Ingress ControllerAn Ingress Controller manages external access to Services within a cluster. It acts as a load balancer that distributes traffic across multiple Pods and handles routing based on defined Ingress rules. It also serves as a reverse proxy that manages TLS certificates and encryption. Having a proxy in front of the load balancer is a common setup in production environments.
Ingress (Networking)An Ingress manages inbound HTTP(S) traffic to Services. You can define an FQDN, configure encryption (TLS), and specify routing rules to forward traffic to the appropriate Service.
PodThe smallest deployable unit in Kubernetes — a Pod runs one or more containers that share the same network and storage.

Init Container:
Runs before the main container to perform setup tasks, such as database migrations. It stops once the initialization is complete.

Sidecar Container:
Runs alongside the main container to handle supporting tasks, such as logging, synchronization, or scheduled jobs.

Sources