Discuss Linux Foundation CKA Exam Topic 1 Question 72

Score: 7%

Task

Create a new nginx Ingress resource as follows:

* Name: ping

* Namespace: ing-internal

* Exposing service hi on path /hi using service port 5678

AExplanation:
Solution:
vi ingress.yaml
#
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ping
namespace: ing-internal
spec:
rules:
- http:
paths:
- path: /hi
pathType: Prefix
backend:
service:
name: hi
port:
number: 5678
#
kubectl create -f ingress.yaml

Suggested Answer: A

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

39 comments · newest first

Matt 11 months ago

I thought Ingress was more complicated than this. Surprised it’s so straightforward!

Veronika 11 months ago

Yup, using pathType: Prefix is the way to go for flexibility!

Florinda 12 months ago

Wait, does the path need to be exactly /hi? What if I want to add more paths later?

Cristy 12 months ago

Looks good! That’s the right way to expose the service.

Ryann 1 year ago

Just created an Ingress resource named 'ping' in the 'ing-internal' namespace.

Wava 1 year ago

I practiced creating Ingress resources, but I’m a bit uncertain about the exact syntax for the backend section.

Lelia 1 year ago

I feel confident about the service name and port, but I might mix up the namespace if I'm not careful.

Hoa 1 year ago

This looks similar to the practice questions we did on Ingress resources, but I can't recall if the pathType is always required.

Alberta 1 year ago

I think I remember that we need to specify the apiVersion and kind correctly, but I'm not entirely sure about the indentation in YAML.

Nobuko 1 year ago

This is a good opportunity to practice creating Ingress resources. I'll give it a try and see if I can get it right.

Yvonne 1 year ago

Wait, do I need to create the `hi` service first before defining it in the Ingress? I better review the steps.

Marleen 1 year ago

Okay, I think I've got this. I'll create the Ingress resource in the `ing-internal` namespace and expose the `hi` service on the `/hi` path.

Candra 1 year ago

Hmm, not sure about the `pathType` field, I'll need to double-check the documentation on that.

Willodean 1 year ago

This looks straightforward, I'll start by creating the YAML file for the Ingress resource.

Margot 1 year ago

I'm pretty sure it's vSphere HA, since Fault Tolerance is all about high availability.

Melinda 2 years ago

I bet the person who came up with this question was feeling a little 'nginx' that day. Get it? *laughs awkwardly*

German 2 years ago

I wonder if the 'ping' Ingress resource is for a health check endpoint. You know, just to make sure the 'hi' service is up and running. *winks*

Teddy 2 years ago

↳ replying to German

Definitely! It's always good to have monitoring in place for critical services like 'hi'.

Lyndia 2 years ago

↳ replying to German

I like the creativity in naming it 'ping'. It's clear and to the point.

Latosha 2 years ago

↳ replying to German

Yes, it's a good way to ensure the 'hi' service is up and running smoothly.

Izetta 2 years ago

↳ replying to German

That's a clever idea! Having a 'ping' Ingress resource for a health check endpoint.

Elsa 2 years ago

This is a piece of cake! I could probably do this in my sleep. *yawns* But seriously, great job on the solution. It's concise and to the point.

Isabelle 2 years ago

↳ replying to Elsa

Definitely, creating a new nginx Ingress resource is not too complicated.

Una 2 years ago

↳ replying to Elsa

I agree, the solution is clear and easy to follow.

Janessa 2 years ago

↳ replying to Elsa

Thanks! Yeah, it's pretty straightforward.

Alyssa 2 years ago

I think the provided solution with creating the Ingress resource in the YAML file is clear and easy to follow.

Santos 2 years ago

Nice! I like how the solution uses the 'pathType: Prefix' option to handle the '/hi' path. That's a good way to ensure the Ingress resource works as expected.

Juan 2 years ago

↳ replying to Santos

Good point! It's a key detail to pay attention to when setting up an Ingress resource.

Bettyann 2 years ago

↳ replying to Santos

Exactly, it's important for ensuring the Ingress resource functions properly with the specified path.

Magnolia 2 years ago

↳ replying to Santos

I agree, it helps to make sure the traffic is correctly routed to the specified service.

Diane 2 years ago

↳ replying to Santos

Thanks! Yes, using 'pathType: Prefix' is a great way to define the path for the Ingress resource.

Malcom 2 years ago

I agree, it requires attention to detail to set it up correctly.

Tarra 2 years ago

The solution is correct, but I'd recommend adding some comments to the YAML file to explain what each section does. That way, it'll be easier to understand if you come back to it later.

Carline 2 years ago

This is a pretty straightforward question. The solution provided looks good, though I'd suggest double-checking the indentation and formatting to ensure the YAML is valid.

Milly 2 years ago

↳ replying to Carline

Once the YAML file is ready, we can create the Ingress resource using kubectl create -f ingress.yaml.

Breana 2 years ago

↳ replying to Carline

Make sure to check the YAML formatting and indentation before creating the Ingress resource.

Cherri 2 years ago

↳ replying to Carline

Yes, we need to expose the service hi on path /hi using service port 5678.

Michel 2 years ago

↳ replying to Carline

Looks simple enough, just need to create a new nginx Ingress resource named ping in the ing-internal namespace.

Alyssa 2 years ago

I found the question on creating a new nginx Ingress resource challenging.

Linux Foundation CKA Exam - Topic 1 Question 72 Discussion