Discuss Linux Foundation CKAD Exam Topic 2 Question 40

Refer to Exhibit.

Set Configuration Context:

[student@node-1] $ | kubectl

Config use-context k8s

Context

A pod is running on the cluster but it is not responding.

Task

The desired behavior is to have Kubemetes restart the pod when an endpoint returns an HTTP 500 on the /healthz endpoint. The service, probe-pod, should never send traffic to the pod while it is failing. Please complete the following:

* The application has an endpoint, /started, that will indicate if it can accept traffic by returning an HTTP 200. If the endpoint returns an HTTP 500, the application has not yet finished initialization.

* The application has another endpoint /healthz that will indicate if the application is still working as expected by returning an HTTP 200. If the endpoint returns an HTTP 500 the application is no longer responsive.

* Configure the probe-pod pod provided to use these endpoints

* The probes should use port 8080

AExplanation:
Solution:
To have Kubernetes automatically restart a pod when an endpoint returns an HTTP 500 on the /healthz endpoint, you will need to configure liveness and readiness probes on the pod.
First, you will need to create a livenessProbe and a readinessProbe in the pod's definition yaml file. The livenessProbe will check the /healthz endpoint, and if it returns an HTTP 500, the pod will be restarted. The readinessProbe will check the /started endpoint, and if it returns an HTTP 500, the pod will not receive traffic.
Here's an example of how you can configure the liveness and readiness probes in the pod definition yaml file:
apiVersion: v1
kind: Pod
metadata:
name: probe-pod
spec:
containers:
- name: probe-pod
image: <image-name>
ports:
- containerPort: 8080
livenessProbe:
httpGet:
path: /healthz
port: 8080
initialDelaySeconds: 15
periodSeconds: 10
failureThreshold: 3
readinessProbe:
httpGet:
path: /started
port: 8080
initialDelaySeconds: 15
periodSeconds: 10
failureThreshold: 3
The httpGet specifies the endpoint to check and the port to use. The initialDelaySeconds is the amount of time the pod will wait before starting the probe. periodSeconds is the amount of time between each probe check, and the failureThreshold is the number of failed probes before the pod is considered unresponsive.
You can use kubectl to create the pod by running the following command:
kubectl apply -f <filename>.yaml
Once the pod is created, Kubernetes will start monitoring it using the configured liveness and readiness probes. If the /healthz endpoint returns an HTTP 500, the pod will be restarted. If the /started endpoint returns an HTTP 500, the pod will not receive traffic.
Please note that if the failure threshold is set to 3, it means that if the probe fails 3 times consecutively it will be considered as a failure.
The above configuration assumes that the application is running on port 8080 and the endpoints are available on the same port.

Suggested Answer: A

Get Premium CKAD Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

36 comments · newest first

Twana 11 months ago

Just to clarify, are both endpoints on port 8080?

Velda 11 months ago

Initial delay of 15 seconds sounds reasonable for startup.

Sharee 12 months ago

Wait, does the failure threshold really need to be 3? Seems high.

Sarah 12 months ago

Totally agree, that's the way to go!

Nana 1 year ago

You need liveness and readiness probes for this!

Quentin 1 year ago

I definitely remember the importance of the /healthz endpoint for liveness checks, but I’m not clear on how to structure the YAML file correctly. Did we cover that in our last session?

Thomasena 1 year ago

I feel a bit confused about the failureThreshold setting. Does it mean the pod will only restart after failing three times, or is it more complex than that?

Ruthann 1 year ago

I think we did a similar question where we had to set up probes for a different application. If I recall correctly, the readiness probe should prevent traffic until the app is ready, right?

Gilma 1 year ago

I remember we practiced configuring liveness and readiness probes, but I'm not entirely sure about the initialDelaySeconds value. Should it be longer for slower applications?

Jame 1 year ago

The key here is to make sure the probes are configured correctly to meet the desired behavior. I'll need to pay close attention to the probe settings like initialDelaySeconds, periodSeconds, and failureThreshold.

Cecily 1 year ago

Okay, I think I've got a good handle on this. I'll set up the livenessProbe to check the /healthz endpoint and the readinessProbe to check the /started endpoint. That should do the trick.

Jaime 1 year ago

Hmm, I'm a bit confused about the difference between the liveness and readiness probes. I'll need to make sure I understand that properly before I can tackle this question.

Quentin 1 year ago

This seems straightforward. I'll need to configure the liveness and readiness probes for the pod based on the provided endpoints and requirements.

Irma 1 year ago

This question seems straightforward, I think I can handle it. I'll start by carefully reading through each option and considering which ones align with an effective risk management culture.

Karma 1 year ago

This seems like a straightforward question about consumer behavior. I think the answer is E - Laggards, since they are the ones who avoid change and stick to traditional products.

Tegan 1 year ago

Ah, I remember learning about Dovecot in my system administration class. The "mail_location" variable is the one that specifies the location of user mail, so I'm confident that option B is the correct answer.

Willodean 1 year ago

Isn't it true that credit risk can vary throughout the swap's life? I feel like that might complicate Widby's suggestion.

Caprice 2 years ago

Kubernetes probes? Piece of cake! I could write the solution in my sleep. *yawns*

Sharee 1 year ago

↳ replying to Caprice

User 3: I agree, it's important to configure them correctly to ensure the pod behaves as expected.

Daren 1 year ago

↳ replying to Caprice

User 2: Yeah, it's all about setting up those liveness and readiness probes in the pod definition yaml file.

Arlene 1 year ago

↳ replying to Caprice

User 1: Wow, you seem confident about Kubernetes probes!

Filiberto 2 years ago

Hmm, I bet the trick is in the details of the probe configuration. Let's see if I can nail this one.

Arleen 2 years ago

This is a good one. I like how it covers both the liveness and readiness probes. Time to put my Kubernetes skills to the test!

Dominque 1 year ago

↳ replying to Arleen

Good luck with your Kubernetes testing, let us know how it goes!

Colette 2 years ago

↳ replying to Arleen

Thanks for the reminder, I'll be careful with the configuration.

Tracey 2 years ago

↳ replying to Arleen

Make sure to double-check your yaml file before applying it.

Portia 2 years ago

↳ replying to Arleen

I agree, this explanation is really helpful. I'm excited to try it out!

Annmarie 2 years ago

The probes sound straightforward, but I wonder if there are any edge cases I should be aware of.

Horace 2 years ago

Ah, finally a question that tests my Kubernetes knowledge! This is right up my alley.

Arlette 1 year ago

↳ replying to Horace

Absolutely, setting up those probes correctly can make a big difference in the performance of the pod.

Vincenza 1 year ago

↳ replying to Horace

Definitely! The configuration for the liveness and readiness probes seems crucial for ensuring the pod's stability.

Kate 1 year ago

↳ replying to Horace

I agree, it's always exciting to learn more about Kubernetes and how it works.

Shaunna 2 years ago

↳ replying to Horace

Great! Kubernetes is such an interesting topic to dive into.

Shawnee 2 years ago

The probes will check the /healthz and /started endpoints to ensure the pod is responsive and ready to receive traffic.

Lynelle 2 years ago

Yes, we should create a livenessProbe and a readinessProbe in the pod's definition yaml file.

Shawnee 2 years ago

I think we need to configure liveness and readiness probes on the pod.

Linux Foundation CKAD Exam - Topic 2 Question 40 Discussion