06 · KubernetesLab 37 / 59
Challengekubernetes
Application Routing with K8s Ingress & AWS Load Balancer Controller — Challenge
Let a Kubernetes manifest provision a real AWS load balancer, and make the application reachable from the internet.
- Time
- 15 min
- Level
- Intermediate
- Objectives
- 4 objectives
- Cost
- Billable
Where this fits in the platform
Already built
This lab adds
- An ALB provisioned by the cluster from an Ingress object
Before you start
Cost — Billable
An Ingress backed by the AWS Load Balancer Controller creates a real ALB at ~$0.0225/hour (~$16/month) plus LCU charges — and it is created by Kubernetes, so `terraform destroy` will not remove it.
The goal#
Build Application Routing with K8s Ingress & AWS Load Balancer Controller yourself, starting from an empty directory, without following the guided steps.
Everything you need is in the criteria above. Work down them one at a time, and verify each before moving to the next.
Hands-on environment
Run it on AWS
This lab builds real cloud infrastructure, so it needs your own AWS account. Follow the cost and cleanup notes above — the resources are yours, and so is the bill.
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.
Rules#
- Do not open the guided lab until you have genuinely tried.
- When something fails, read the error before you search. The error message is the lesson.
- Tear down anything billable as soon as you finish.
If you get stuck#
The guided lab is one click away at the bottom of this page. Using it is not failure — coming back and repeating the challenge afterwards is the point.
You are done when
0 of 4
The concept behind it
Next up
Lab 37 of 59 on the project path