Endpoints and endpoint slices in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Kubernetes Endpoint?

An Endpoint in Kubernetes is a resource that lists the IP addresses and ports of the pods that are matched by a Service selector. It helps route traffic to the right pods.

intermediate

What problem do Endpoint Slices solve compared to Endpoints?

Endpoint Slices improve scalability and performance by splitting large Endpoint lists into smaller chunks. This reduces load on the API server and improves network efficiency.

intermediate

How does Kubernetes use Endpoint Slices internally?

Kubernetes automatically creates Endpoint Slices for Services. Each slice contains a subset of the pods' IPs and ports, allowing clients to discover endpoints efficiently.

beginner

What is the main difference between Endpoints and Endpoint Slices in Kubernetes?

Endpoints store all pod IPs in one resource, while Endpoint Slices split them into multiple smaller resources. Endpoint Slices are the newer, more scalable way to track pod endpoints.

beginner

How can you view Endpoint Slices for a Service in Kubernetes?

You can run the command kubectl get endpointslices -n <namespace> to list Endpoint Slices. They are labeled with the Service name for easy identification.

What does a Kubernetes Endpoint resource represent?

A A container image registry

B A list of pod IPs and ports matched by a Service

C A configuration file for pods

D A network policy

Endpoints list the IP addresses and ports of pods that a Service routes to.

Why were Endpoint Slices introduced in Kubernetes?

A To improve scalability and reduce API server load

B To replace pods

C To store container logs

D To manage persistent storage

Endpoint Slices split large endpoint lists into smaller parts to improve scalability.

Which command lists Endpoint Slices in a Kubernetes namespace?

A kubectl get endpointslices -n <namespace>

B kubectl get pods -n <namespace>

C kubectl describe service <name>

D kubectl get nodes

The command 'kubectl get endpointslices' shows Endpoint Slices.

How do Endpoint Slices improve network efficiency?

A By encrypting network traffic

B By compressing pod logs

C By grouping endpoints into smaller chunks

D By caching container images

Smaller groups of endpoints reduce the data clients need to process.

What label helps identify Endpoint Slices belonging to a Service?

A kubernetes.io/hostname

B app.kubernetes.io/version

C node-role.kubernetes.io/master

D kubernetes.io/service-name

Endpoint Slices are labeled with 'kubernetes.io/service-name' to link them to Services.

Explain what Kubernetes Endpoints and Endpoint Slices are and why Endpoint Slices are preferred in large clusters.

Think about how Kubernetes tracks pods for Services and how it handles many pods.

Describe how you would check the Endpoint Slices for a Service in your Kubernetes cluster.

Use kubectl get endpointslices and check labels.

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