Conversation
|
At this point the first steps working with Helm have been taken. I'm still exposing the Traefik Gateway to the host network but no longer on port Using the official Traefik Helm Chart abstracts away quite a bit. It's pulled in as a dependency that Helm then automatically stores as a compressed file under Next I'm going to try setting up cert-manager with the DNS Challenge so I can request SSL certificates from my local as well as my production clusters using the same configuration. |
|
Spinning up the cluster is now as simple as running |
I'm just getting started on my Kubernetes journey and have decided to go with k3s as I intend to run that in production later on as well. The goal is to stay as close to production as possible while not making things unnecessarily complicated in local development. I think I've found a nice middle ground by exposing the Gateway to the host network similarly to how it's convention to expose services from a
docker-compose.yamlfile.