Serve an App over HTTPS with Ingress

medium 20 XP ~8 minHands-on lab

Security issued a certificate for catalog.audit.example.lab: /home/student/catalog-tls.crt and /home/student/catalog-tls.key. The Service catalog in audit already exists, and the cluster's ingress controller uses the IngressClass nginx.

Task

Store the certificate and key in a TLS Secret catalog-tls in audit.
Create an Ingress catalog in audit with the class nginx that serves https://catalog.audit.example.lab/ using that Secret and sends all paths (/, prefix) to the Service catalog on port 80.
Plain HTTP requests must be redirected to HTTPS. Use the annotation nginx.ingress.kubernetes.io/ssl-redirect: "true".

Start with openssl x509 -in /home/student/catalog-tls.crt -noout -subject.

About this machine

Ubuntu 24.04 with a private practice cluster: a real Kubernetes API server, scheduler and controllers, and three nodes (controlplane, node01, node02). Containers are simulated, so images never download and kubectl logs/exec are not available. k is an alias for kubectl, with completion. The grader checks the cluster's final state, not the commands you typed.

ingress tls secrets cka