Kubernetes Services

5 minutes 5 Questions

Kubernetes Services are a fundamental abstraction that enables reliable network communication between different components in a Kubernetes cluster. As a Google Cloud Associate Cloud Engineer, understanding Services is essential for managing applications on Google Kubernetes Engine (GKE). A Service provides a stable endpoint (IP address and DNS name) for accessing a set of Pods, which are ephemeral by nature. Since Pods can be created, destroyed, or rescheduled at any time, their IP addresses change frequently. Services solve this problem by providing a consistent way to reach your applications. There are four main types of Kubernetes Services: 1. **ClusterIP**: The default type that exposes the Service on an internal IP address within the cluster. This is ideal for internal communication between microservices. 2. **NodePort**: Exposes the Service on each node's IP at a static port. External traffic can access the Service by connecting to any node's IP address on the designated port. 3. **LoadBalancer**: Provisions an external load balancer (in GKE, this creates a Google Cloud Load Balancer) that routes external traffic to your Service. This is the standard method for exposing applications to the internet. 4. **ExternalName**: Maps a Service to an external DNS name, allowing pods to reference external services using Kubernetes-native methods. Services use label selectors to determine which Pods should receive traffic. When traffic arrives at a Service, it is distributed across healthy Pods matching the selector criteria using kube-proxy. For successful cloud operations, you should monitor Service health, configure appropriate health checks, and understand how Services integrate with GKE features like Ingress controllers for advanced HTTP routing. Properly configured Services ensure high availability, load distribution, and seamless scaling of your containerized applications on Google Cloud Platform.

Kubernetes Services: A Complete Guide for GCP Associate Cloud Engineer Exam

Why Kubernetes Services are Important

Kubernetes Services are fundamental to running applications in production environments. Pods in Kubernetes are ephemeral - they can be created, destroyed, and replaced at any time. This means their IP addresses change frequently. Services provide a stable networking endpoint that allows reliable communication between different parts of your application and external users, regardless of which pods are running behind them.

What is a Kubernetes Service?

A Kubernetes Service is an abstraction that defines a logical set of Pods and a policy for accessing them. It provides:
- A stable IP address and DNS name
- Load balancing across multiple pods
- Service discovery within the cluster
- A way to expose applications to external traffic

Types of Kubernetes Services

1. ClusterIP (Default)
- Exposes the service on an internal IP within the cluster
- Only accessible from within the cluster
- Best for internal communication between microservices

2. NodePort
- Exposes the service on each node's IP at a static port (30000-32767)
- Accessible from outside the cluster using NodeIP:NodePort
- Automatically creates a ClusterIP service

3. LoadBalancer
- Provisions an external load balancer (in GCP, this creates a Network Load Balancer)
- Assigns a public IP address to the service
- Automatically creates NodePort and ClusterIP services
- Most common choice for production workloads on GKE

4. ExternalName
- Maps a service to a DNS name
- Returns a CNAME record
- Used for accessing external services from within the cluster

How Kubernetes Services Work

Services use selectors to identify which pods should receive traffic. The selector matches labels on pods. For example:

A service with selector app: frontend will route traffic to all pods that have the label app: frontend.

Kubernetes maintains an Endpoints object that tracks the IP addresses of healthy pods matching the selector. The kube-proxy component on each node programs network rules to route traffic to the appropriate pods.

Key Concepts for GKE

- Ingress: While not a Service type, Ingress works with Services to provide HTTP/HTTPS routing, SSL termination, and name-based virtual hosting
- Network Endpoint Groups (NEGs): GKE can use NEGs for more efficient load balancing
- Internal Load Balancer: Created by adding an annotation to a LoadBalancer service for internal-only access

Exam Tips: Answering Questions on Kubernetes Services

Tip 1: Know the Service Type Hierarchy
Remember that LoadBalancer includes NodePort, which includes ClusterIP. When a question asks about external access with load balancing, LoadBalancer is typically correct.

Tip 2: Match Use Cases to Service Types
- Internal microservice communication → ClusterIP
- Development/testing external access → NodePort
- Production external access → LoadBalancer
- Mapping to external DNS → ExternalName

Tip 3: Understand GKE-Specific Features
Questions may reference GKE-specific implementations like Container-native load balancing or integration with Cloud Load Balancing.

Tip 4: Pay Attention to Keywords
- Internal only → ClusterIP or Internal LoadBalancer
- External traffic → LoadBalancer or NodePort
- Stable endpoint → Any Service type
- HTTP/HTTPS routing → Consider Ingress with Services

Tip 5: Remember Port Ranges
NodePort uses ports 30000-32767 by default. This detail sometimes appears in exam questions.

Tip 6: Labels and Selectors
Services find pods through label selectors. If a question involves pods not receiving traffic, check if labels match between the Service selector and Pod labels.
Test mode:
More Kubernetes Services questions
30 questions (total)

Other Ensuring Successful Operation of a Cloud Solution concepts

Active Assist for resource utilizationAdding a subnet to an existing VPCAdding custom static routes in a VPCAdding, editing, and removing node poolsAdjusting application traffic splittingAutoscaling node poolsBacking up and restoring database instancesCloud ProfilerCloud TraceConfiguring and deploying Ops AgentConfiguring audit logsConfiguring autoscaling for Cloud RunConfiguring GKE to access Artifact RegistryConfiguring log bucketsCreating and viewing imagesCreating Cloud Monitoring alertsCreating Cloud Monitoring custom metricsDeploying new Cloud Run application versionsEstimating costs of data storage resourcesExecuting queries to retrieve dataExpanding a subnet for more IP addressesExporting logs to BigQueryExporting logs to external systemsGemini Cloud Assist for Cloud MonitoringGKE nodes, Pods, and ServicesGoogle Cloud Managed Service for PrometheusHorizontal Pod autoscalingIndex advisorIngesting custom metrics from applicationsKubernetes PodsKubernetes StatefulSetsLog analyticsLog routersManaging GKE Autopilot Pod resource requestsManaging objects in Cloud Storage bucketsObject lifecycle management policiesPersonalized Service Health dashboardQuerying AlloyDBQuerying BigQueryQuerying BigtableQuerying Cloud SQLQuerying FirestoreQuerying SpannerQuery InsightsRemotely connecting to Compute Engine instancesReserving static external IP addressesReserving static internal IP addressesReviewing job status (Dataflow, BigQuery)Scheduling snapshotsSecuring objects in Cloud Storage bucketsUsing Database CenterVertical Pod autoscalingViewing and filtering logs in Cloud LoggingViewing GKE cluster inventoryViewing log message detailsViewing running Compute Engine instancesWorking with Cloud DNSWorking with Cloud NATWorking with GKE node poolsWorking with Kubernetes resourcesWorking with snapshots and images