06 · KubernetesLab 38 / 59
Challengekubernetes
From Ingress to Gateway API — Challenge
Express the same routing twice — as an Ingress and as a Gateway — and see what the newer model actually fixes.
- Time
- 25 min
- Level
- Intermediate
- Objectives
- 4 objectives
- Cost
- Free
Where this fits in the platform
This lab adds
- The same routing expressed in the API that replaces Ingress
Which lets you
—
Before you start
You will need
- kind or minikube
- kubectl 1.28+
- A Gateway API controller (Envoy Gateway or NGINX Gateway Fabric)
You do not need these already — the lab environment below provides them.
You will be able to
- Write a Gateway and an HTTPRoute for an existing Service
- Explain the role split Gateway API introduces
- Do a weighted traffic split without controller-specific annotations
The goal#
Achieve the same outcome as From Ingress to Gateway API, from an empty starting point, without the steps.
Ingress is stable, everywhere, and feature-frozen. Everything it cannot express — header matching, traffic splitting, timeouts — moved into vendor annotations that mean different things on different controllers.
Gateway API is the replacement. Learn Ingress first, because it is what existing clusters run; learn this, because new ones will not.
Hands-on environment
Run this lab in a real terminal, free and in your browser. The environment is temporary and yours alone — break it as much as you like.
Start the challengeOpens in Killercoda, in a new tab — keep this page open for the steps.
This is the guided lab's environment — the same machine, with its walkthrough on the left. Work from the task above and leave those steps alone until you are done, or you are reading the answers.
Run it on your own machine
Run this lab on your own machine. One command starts the environment, with everything the lab needs already installed:
You will need:
- docker
- kubectl
- kind
git clone https://github.com/EgyKode/EgyKode-lab.git
cd EgyKode-lab
./egykode start k8s
./egykode shellYou need Docker and Git installed. Everything else runs inside the environment. The first start downloads it and takes a few minutes; later starts are seconds.
Not sure what you already have? Run: npm run doctor — it checks and changes nothing.
Anything you tick here is your own record. EgyKode cannot see inside that terminal, so the success criteria stay self-assessed even when the environment checks your work for you.
What must be true when you are done
Step 1 of 3
What must be true when you are done#
- The same application is reachable through an Ingress and through an HTTPRoute.
- A weighted split sends traffic to two Services, with no annotations.
- You can name two things Gateway API expresses that Ingress cannot.
- You can explain who owns a Gateway versus who owns an HTTPRoute.
Rules#
- Do not open the guided lab until you are finished, or until the same problem has held you up for 20 minutes.
- Documentation is allowed and encouraged.
- Verify every criterion with a command whose output you can read.
If you get stuck#
- What did you expect, exactly?
- What happened instead — the error text, not a paraphrase?
- Which layer is that error from?
- What is the smallest command that proves the layer below is fine?
You are done when
0 of 4
The concept behind it
Next up
Lab 38 of 59 on the project path