Skip to content
CKADServices and NetworkingSingle nodeEasy

Service with no working endpoints

Scenario ckad-net-004 · about 6 minutes · 7 points · 7 grader checks

Find why a Service does not reach the pods of a healthy Deployment and fix the Service.

  • service
  • troubleshooting
  • selectors
  • endpoints

What you will practise

  • Compare a Service selector with pod labels
  • Check Service port and targetPort against the container port
  • Verify the result with EndpointSlices and an HTTP request

Start this lab

With the CLI installed and signed in, this command provisions a single node cluster on your Mac, applies the scenario setup and prints the task below.

goldenkube start ckad-net-004

Task

The task text exactly as the CLI shows it. Solve it on the cluster, then run goldenkube submit.

In namespace "svc-debug" the Deployment "payments" (image nginx:1.27, 2 replicas, nginx listens on port 80) runs fine, but requests to the Service "payments" on port 80 never reach it. Fix the Service "payments" so that it sends traffic on port 80 to the pods of the Deployment "payments". Do not change the Deployment. When you are done both pods must be Ready endpoints of the Service and an HTTP request from the node exam-cp1 to the Service's cluster IP on port 80 must be answered by nginx.

Requirements and details

Certification
CKAD · Certified Kubernetes Application Developer
Domain
Services and Networking
Difficulty
Easy
Cluster topology
Single node
Cluster features
None beyond the base cluster
Recommended time
6 minutes
Points
7
Grader checks
7
Kubernetes version
1.37
Minimum CLI version
0.1.0
Scenario version
1
Published

Grading runs locally: 7 state checks read your cluster when you submit; the scenario passes when every check passes. Hints, the reference solution and the check definitions are available only inside the CLI, not on this page.

CKADServices and NetworkingEasy

Expose a Deployment with ClusterIP and NodePort Services

Expose the same pods through a ClusterIP Service with port mapping and a NodePort Service on a fixed node port.

Single node · ~6 min · 9 points

  • service
  • clusterip
  • nodeport
  • endpoints

goldenkube start ckad-net-001

CKADServices and NetworkingMedium

NetworkPolicy: default deny plus one allowed client

Lock down a namespace with a default-deny ingress policy and allow a single client label to reach an API on one port.

Single node · ~8 min · 8 points

  • networkpolicy
  • default-deny
  • ingress
  • labels
  • networking

goldenkube start ckad-net-002

CKADServices and NetworkingMedium

Ingress with two paths and TLS

Expose two Services under one host with path-based Ingress rules and terminate TLS with a certificate Secret.

Single node · ~8 min · 9 points · Ingress

  • ingress
  • tls
  • secret
  • path-routing
  • networking

goldenkube start ckad-net-003

Independent community project, not affiliated with or endorsed by CNCF or The Linux Foundation. Lab results are practice feedback, not an exam score.