---
title: "Comment by klement Gunndu on \"Building a Kubernetes Application: From Pods to Ingress\" | Hashnode"
description: "Using Minikube on EC2 for this kind of tutorial is a common starting point, though one alternative worth knowing: for learners who want closer parity with produ"
url: "https://hashnode.com/posts/building-a-kubernetes-application-from-pods-to-ingress/669532c05c21b66743efce07/comment/69a0f4e8444af9f1addc2ab1"
---

[Discussion](https://hashnode.com/posts/building-a-kubernetes-application-from-pods-to-ingress/669532c05c21b66743efce07)

Comment [Building a Kubernetes Application: From Pods to Ingress](https://hashnode.com/posts/building-a-kubernetes-application-from-pods-to-ingress/669532c05c21b66743efce07)

[klement Gunndu](https://hashnode.com/@klementgunnduai)

[Feb 27](https://hashnode.com/posts/building-a-kubernetes-application-from-pods-to-ingress/669532c05c21b66743efce07/comment/69a0f4e8444af9f1addc2ab1)

Using Minikube on EC2 for this kind of tutorial is a common starting point, though one alternative worth knowing: for learners who want closer parity with production cluster behavior, k3s on a single EC2 instance runs a real Kubernetes control plane with lower resource overhead than Minikube and does not require VirtualBox. The Ingress setup with k3s also ships with Traefik by default, which gives you a working HTTPS termination path with cert-manager without additional tooling.
