“ClusterIP: This is the default type. A virtual IP address that can be accessed only within the cluster is allocated from the Service CIDR block of the cluster.”
[Course note] If pods need to communicate with each other in a cluster, you can create a ClusterIP Service.
Huawei source: Training PDF p. 458
Technical Deep Dive
ClusterIP is Kubernetes' default Service type, and Huawei CCE assigns it a virtual IP from the cluster's Service CIDR. That virtual address is intended for access inside the cluster. Option B is therefore correct. A frontend pod, for example, can reach a backend payment Service through a stable DNS name and ClusterIP without tracking changes to individual backend pod IP addresses.
A Kubernetes Service normally selects eligible pods by label, while associated EndpointSlice resources track their current network endpoints. If a backend pod is deleted and replaced, the Service stays in place and eligible endpoints are updated. A standard ClusterIP manifest declares spec.type: ClusterIP and a port-to-targetPort mapping. Operators can inspect it using kubectl get svc and kubectl describe svc. Option C , NodePort, opens an access port on nodes and therefore does not describe internal-only Service exposure. Option D , LoadBalancer, provisions or connects to a load balancing resource for access beyond the internal ClusterIP mechanism. Option A , an NGINX ingress controller, routes ingress HTTP/HTTPS traffic and is not the Service type described.
A ClusterIP address by itself should not be confused with a strong security boundary: network policy and cluster admission controls may still be needed. The virtual IP is only one abstraction in a wider Kubernetes service-discovery and routing model. The decisive clue is the default internal virtual IP from the Service CIDR; that uniquely identifies ClusterIP under Huawei's training.
Technical commands / calculations from the reviewed batch
apiVersion: v1
kind: Service
metadata:
name: payment-service
spec:
type: ClusterIP
selector:
app: payment
ports:
- port: 80
targetPort: 8080
Submit