Why Ingress manages external access in Kubernetes - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define an Ingress resource that manages external access.

Kubernetes

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: example-ingress
spec:
  [1]:
  - host: example.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: example-service
            port:
              number: 80

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

Aports

Bservices

Crules

Dendpoints

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'services' instead of 'rules' causes a syntax error.

Confusing 'endpoints' with Ingress routing rules.

The rules field defines how Ingress routes external traffic to services inside the cluster.

2fill in blank

medium

Complete the code to specify the backend service port in the Ingress.

Kubernetes

spec:
  rules:
  - host: example.com
    http:
      paths:
      - path: /app
        pathType: Prefix
        backend:
          service:
            name: app-service
            port:
              number: [1]

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

A80

B443

C22

D8080

Attempts:

3 left

💡 Hint

Common Mistakes

Using port 22 (SSH) causes connection failure.

Using port 443 without TLS configuration causes errors.

Port 80 is the standard HTTP port used for web traffic in Ingress backend services.

3fill in blank

hard

Fix the error in the Ingress pathType to correctly route traffic.

Kubernetes

spec:
  rules:
  - host: example.com
    http:
      paths:
      - path: /api
        pathType: [1]
        backend:
          service:
            name: api-service
            port:
              number: 80

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

AExact

BPrefix

CRegex

DContains

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Regex' causes syntax errors as it's not supported in this version.

Using 'Contains' is invalid pathType.

The Prefix pathType matches all paths that start with the given prefix, which is commonly used in Ingress.

4fill in blank

hard

Fill both blanks to configure TLS for Ingress external access.

Kubernetes

spec:
  tls:
  - hosts:
    - [1]
    secretName: [2]

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

Aexample.com

Bmy-tls-secret

Cdefault-secret

Dmy-service

Attempts:

3 left

💡 Hint

Common Mistakes

Using service name instead of secret name for TLS.

Using wrong domain name in hosts causes TLS errors.

The hosts field lists the domain names for TLS, and secretName specifies the TLS certificate secret.

5fill in blank

hard

Fill all three blanks to create an Ingress rule that routes traffic to a service on a specific path.

Kubernetes

spec:
  rules:
  - host: [1]
    http:
      paths:
      - path: [2]
        pathType: [3]
        backend:
          service:
            name: web-service
            port:
              number: 80

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

Amyapp.example.com

B/web

CPrefix

D/api

Attempts:

3 left

💡 Hint

Common Mistakes

Using path without leading slash causes routing failure.

Using 'Exact' pathType when prefix matching is needed.

The host is the domain name, path is the URL path to match, and pathType defines how the path is matched.

Practice

1. What is the primary role of an Ingress in Kubernetes?

easy

A. To manage external access to services inside the cluster

B. To store configuration data for pods

C. To schedule pods on nodes

D. To monitor resource usage of containers

Solution

1. Step 1: Understand Ingress purpose

   Ingress is designed to control how external users access services running inside Kubernetes.

2. Step 2: Compare with other components

   Other components like ConfigMaps store data, schedulers place pods, and metrics monitor usage, but Ingress manages external access.

3. Final Answer:

   To manage external access to services inside the cluster -> Option A

4. Quick Check:

   Ingress controls external access = C [OK]

Hint: Ingress controls outside traffic to services [OK]

Common Mistakes:

• Confusing Ingress with ConfigMap or Scheduler
• Thinking Ingress manages internal pod scheduling
• Assuming Ingress monitors resource usage

2. Which of the following is the correct basic syntax to define an Ingress resource in YAML?

easy

A. apiVersion: v1\nkind: Service\nmetadata:\n name: example-ingress\nspec:\n selector:\n app: example\n ports:\n - protocol: TCP\n port: 80\n targetPort: 9376

B. apiVersion: networking.k8s.io/v1\nkind: Ingress\nmetadata:\n name: example-ingress\nspec:\n rules:\n - host: example.com\n http:\n paths:\n - path: /\n pathType: Prefix\n backend:\n service:\n name: example-service\n port:\n number: 80

C. apiVersion: apps/v1\nkind: Deployment\nmetadata:\n name: example-ingress\nspec:\n replicas: 3\n selector:\n matchLabels:\n app: example

D. apiVersion: networking.k8s.io/v1\nkind: Ingress\nmetadata:\n name: example-ingress\nspec:\n rules:\n - host: example.com\n tcp:\n ports:\n - port: 80\n backend:\n serviceName: example-service\n servicePort: 80

Solution

1. Step 1: Identify correct Ingress syntax

   Ingress uses apiVersion networking.k8s.io/v1, kind Ingress, and defines rules with host and http paths.

2. Step 2: Check options for correct fields

   apiVersion: networking.k8s.io/v1\nkind: Ingress\nmetadata:\n name: example-ingress\nspec:\n rules:\n - host: example.com\n http:\n paths:\n - path: /\n pathType: Prefix\n backend:\n service:\n name: example-service\n port:\n number: 80 matches the correct structure with service name and port under backend. apiVersion: v1\nkind: Service\nmetadata:\n name: example-ingress\nspec:\n selector:\n app: example\n ports:\n - protocol: TCP\n port: 80\n targetPort: 9376 is a Service definition. The other options define a Deployment or incorrectly use a tcp field.

3. Final Answer:

   apiVersion: networking.k8s.io/v1 kind: Ingress spec: rules: - host: example.com http: paths: - path: / pathType: Prefix backend: service: name: example-service port: number: 80 -> Option B

4. Quick Check:

   Ingress YAML syntax = A [OK]

Hint: Ingress YAML uses rules with host and http paths [OK]

Common Mistakes:

• Confusing Service or Deployment YAML with Ingress
• Using tcp instead of http in rules
• Incorrect apiVersion or kind for Ingress

3. Given this Ingress rule snippet, what hostname will route traffic to my-service?

spec:
  rules:
  - host: app.example.com
    http:
      paths:
      - path: /app
        pathType: Prefix
        backend:
          service:
            name: my-service
            port:
              number: 8080

medium

A. app.example.com

B. example.com

C. my-service

D. app

Solution

1. Step 1: Identify the host in the Ingress rule

   The host field is set to app.example.com, which defines the hostname for routing.

2. Step 2: Understand routing based on host

   Traffic to app.example.com with path prefix /app routes to my-service on port 8080.

3. Final Answer:

   app.example.com -> Option A

4. Quick Check:

   Host in rule = app.example.com [OK]

Hint: Look for host field in Ingress rules [OK]

Common Mistakes:

• Confusing service name with hostname
• Ignoring the host field and picking path or service name
• Choosing partial strings like 'app' instead of full hostname

4. You created an Ingress resource but external traffic is not reaching your service. Which of these is a likely cause?

medium

A. The pod image is missing a label

B. The cluster has no nodes

C. The service port is set to 0

D. The Ingress controller is not installed or running

Solution

1. Step 1: Check Ingress controller presence

   Ingress resources need an Ingress controller to process rules and route traffic. Without it, Ingress does nothing.

2. Step 2: Evaluate other options

   Pod labels or service ports affect internal routing but won't stop Ingress from receiving traffic. No nodes means cluster is down, but question focuses on Ingress.

3. Final Answer:

   The Ingress controller is not installed or running -> Option D

4. Quick Check:

   Ingress needs controller to route traffic = B [OK]

Hint: Ingress needs a controller running to work [OK]

Common Mistakes:

• Ignoring the need for an Ingress controller
• Blaming pod labels for external access issues
• Confusing service port 0 with Ingress failure

5. You want to expose two services, service-a and service-b, on the same domain but different paths using Ingress. Which configuration correctly achieves this?

hard

A. Use a LoadBalancer service type for each service instead of Ingress

B. Create two Ingress resources with the same host example.com, each with one path for service-a and service-b

C. Define one Ingress with rules for host example.com and paths /a routing to service-a, /b routing to service-b

D. Expose service-a and service-b on different ports without Ingress

Solution

1. Step 1: Understand Ingress path routing

   Ingress can route different URL paths on the same host to different services using rules with multiple paths.

2. Step 2: Compare options for best practice

   Define one Ingress with rules for host example.com and paths /a routing to service-a, /b routing to service-b uses one Ingress with multiple paths, which is efficient and standard. Create two Ingress resources with the same host example.com, each with one path for service-a and service-b may cause conflicts. Options C and D avoid Ingress and don't meet the requirement.

3. Final Answer:

   Define one Ingress with rules for host example.com and paths /a and /b routing to respective services -> Option C

4. Quick Check:

   One Ingress, multiple paths = A [OK]

Hint: Use one Ingress with multiple paths for same host [OK]

Common Mistakes:

• Creating multiple Ingresses with same host causing conflicts
• Using LoadBalancer instead of Ingress for path routing
• Exposing services on different ports without hostname routing