Services & networking
⏱ ~3-min readAceMark Guide
What this topic is really about
An Ingress manages external access to services within a Kubernetes cluster, typically by providing HTTP and HTTPS routing, load balancing, and SSL/TLS termination. In contrast, persistent storage is handled by PersistentVolumes, and VM management is outside the scope of standard Kubernetes Ingress objects.
NetworkPolicies specify how groups of pods are allowed to communicate with each other and other network endpoints at the IP address or port level (L3/L4). They are not mandatory by default, as Kubernetes clusters allow all pod-to-pod communication unless a policy is explicitly applied.
See the mechanism
ClusterIP is the default Kubernetes service type, exposing the service on an internal IP that is only reachable from within the cluster. A diagram for this topic isn't available yet — the worked example below walks the same reasoning step by step.
An exam-style question, fully explained
A Service of type ClusterIP:
- Identify what the question tests: A Service of type ClusterIP:.
- ClusterIP is the default Kubernetes service type, exposing the service on an internal IP that is only reachable from within the cluster.
- It does not expose applications to the public internet, which instead requires a service type like LoadBalancer or NodePort.
Traps the examiner sets
- Option A is wrong because LoadBalancer is not limited to internal traffic; it specifically provisions a cloud LB rather than staying only in-cluster.
Test your recall
Answer each from memory — you'll see instantly whether you're right and why.
Run a focused 10-question mini-mock on Services & networking and see it stick.
Practice more of this topic →