Endpoints and endpoint slices in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to list all endpoints in the default namespace.

Kubernetes

kubectl get [1] -n default

Drag options to blanks, or click blank then click option'

Apods

Bservices

Cendpoints

Dnodes

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pods' instead of 'endpoints' will list pods, not endpoints.

Using 'services' lists services, not their endpoints.

The kubectl get endpoints command lists all endpoints in the specified namespace.

2fill in blank

medium

Complete the command to describe the endpoint slice named 'example-slice' in the 'prod' namespace.

Kubernetes

kubectl describe [1] example-slice -n prod

Drag options to blanks, or click blank then click option'

Aendpoints

Bendpointslices

Cendpointslice

Dendpointslices.k8s.io

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'endpoints' describes endpoints, not endpoint slices.

Using singular 'endpointslice' is invalid resource name.

The resource name for endpoint slices is endpointslices. This command shows detailed info about the slice.

3fill in blank

hard

Fix the error in the command to get endpoint slices in all namespaces.

Kubernetes

kubectl get [1] --all-namespaces

Drag options to blanks, or click blank then click option'

Aendpointslices

Bendpointslice

Cendpoints

Dendpoint-slices

Attempts:

3 left

💡 Hint

Common Mistakes

Using singular or hyphenated names causes errors.

Using 'endpoints' lists endpoints, not endpoint slices.

The correct resource name is endpointslices (plural, no hyphen). This lists all endpoint slices across namespaces.

4fill in blank

hard

Fill both blanks to create an endpoint slice with the name 'my-slice' in the 'test' namespace.

Kubernetes

kubectl create [1] my-slice -n test --address-type=[2]

Drag options to blanks, or click blank then click option'

Aendpointslice

Bendpointslices

CIPv4

DIPv6

Attempts:

3 left

💡 Hint

Common Mistakes

Using singular 'endpointslice' causes command failure.

Using invalid address types causes errors.

Use endpointslices to create the resource. The address type IPv4 specifies the IP version for the slice.

5fill in blank

hard

Fill all three blanks to filter endpoint slices by label 'app=web' and output only their names.

Kubernetes

kubectl get [1] -l [2] -o [3]

Drag options to blanks, or click blank then click option'

Aendpointslices

Bapp=web

Cname

Dnames

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'names' instead of 'name' for output format causes errors.

Using wrong resource names or label selectors returns no results.

Use endpointslices as the resource, filter with label app=web, and output only the name field.

Practice

1. What is the primary purpose of Kubernetes Endpoints?

easy

A. To list the IP addresses of pods behind a service

B. To store configuration data for pods

C. To manage persistent storage volumes

D. To schedule pods on nodes

Solution

1. Step 1: Understand the role of Endpoints in Kubernetes

   Endpoints represent the IP addresses of pods that a service routes traffic to.

2. Step 2: Differentiate Endpoints from other Kubernetes objects

   Endpoints do not manage storage, scheduling, or configuration; they only list pod IPs behind a service.

3. Final Answer:

   To list the IP addresses of pods behind a service -> Option A

4. Quick Check:

   Endpoints = Pod IP list [OK]

Hint: Endpoints show pod IPs for services [OK]

Common Mistakes:

• Confusing Endpoints with ConfigMaps
• Thinking Endpoints manage storage
• Assuming Endpoints schedule pods

2. Which kubectl command correctly lists EndpointSlices in the default namespace?

easy

A. kubectl describe endpointslices

B. kubectl get endpointslices -n default

C. kubectl get endpointslices

D. kubectl get endpoints -n default

Solution

1. Step 1: Identify the correct resource name for EndpointSlices

   The resource name is 'endpointslices' (all lowercase, plural).

2. Step 2: Use kubectl get with namespace option

   To list EndpointSlices in the default namespace, use 'kubectl get endpointslices -n default'.

3. Final Answer:

   kubectl get endpointslices -n default -> Option B

4. Quick Check:

   Correct resource and namespace flag = kubectl get endpointslices -n default [OK]

Hint: Use 'kubectl get endpointslices -n default' to list EndpointSlices [OK]

Common Mistakes:

• Omitting the namespace flag when needed
• Using 'endpoints' instead of 'endpointslices'
• Using describe instead of get for listing

3. Given the following command output, what does it indicate about the service 'webapp'?

kubectl get endpoints webapp
NAME     ENDPOINTS           AGE
webapp   10.1.2.3:80,10.1.2.4:80   5m

medium

A. The service 'webapp' is using EndpointSlices instead of Endpoints

B. The service 'webapp' is not connected to any pods

C. The service 'webapp' has pods but no ports exposed

D. The service 'webapp' has two pods with IPs 10.1.2.3 and 10.1.2.4 serving on port 80

Solution

1. Step 1: Analyze the 'kubectl get endpoints' output

   The output shows two IP addresses with port 80 listed under ENDPOINTS for 'webapp'.

2. Step 2: Interpret the meaning of listed endpoints

   This means the service routes traffic to two pods at IPs 10.1.2.3 and 10.1.2.4 on port 80.

3. Final Answer:

   The service 'webapp' has two pods with IPs 10.1.2.3 and 10.1.2.4 serving on port 80 -> Option D

4. Quick Check:

   Endpoints list pod IPs and ports = The service 'webapp' has two pods with IPs 10.1.2.3 and 10.1.2.4 serving on port 80 [OK]

Hint: Endpoints output shows pod IPs and ports behind service [OK]

Common Mistakes:

• Assuming no pods are connected when endpoints are listed
• Confusing EndpointSlices with Endpoints output
• Ignoring port numbers in the output

4. You run kubectl get endpointslices but see no output, even though your service has pods running. What is a likely cause?

medium

A. Pods are not running on any node

B. EndpointSlices feature is disabled in the cluster

C. The service has no selector labels

D. kubectl command is misspelled

Solution

1. Step 1: Recall when EndpointSlices are created

   EndpointSlices are created only for services with selectors that match ready pods, generating endpoints.

2. Step 2: Identify cause of empty output

   No selector labels means no automatic endpoints/EndpointSlices, resulting in no output (empty list). Feature disabled would error, not empty list.

3. Final Answer:

   The service has no selector labels -> Option C

4. Quick Check:

   No service selector = no EndpointSlices [OK]

Hint: No EndpointSlices despite pods? Check service selector matches pod labels [OK]

Common Mistakes:

• Assuming feature disabled (causes API error, not empty list)
• Thinking pods not running (contradicts premise)
• Blaming kubectl misspelling

5. How do EndpointSlices improve Kubernetes service scalability compared to Endpoints?

hard

A. By splitting endpoints into smaller groups to reduce load on the API server

B. By caching pod IPs locally on each node

C. By replacing services with direct pod IP access

D. By encrypting endpoint data for security

Solution

1. Step 1: Understand the limitation of Endpoints with many pods

   Endpoints list all pod IPs in one object, which can become large and heavy to manage.

2. Step 2: Explain how EndpointSlices address this

   EndpointSlices split the endpoints into smaller chunks, reducing load on the API server and improving performance.

3. Final Answer:

   By splitting endpoints into smaller groups to reduce load on the API server -> Option A

4. Quick Check:

   EndpointSlices split endpoints for scalability [OK]

Hint: EndpointSlices split endpoints to reduce API load [OK]

Common Mistakes:

• Thinking EndpointSlices cache IPs locally
• Believing EndpointSlices replace services
• Assuming EndpointSlices encrypt data