Skip to content

Conversation

@99linesofcode
Copy link
Owner

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.yaml file.

@99linesofcode
Copy link
Owner Author

99linesofcode commented Jun 25, 2025

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 80 and 443 but on the default ports: 8000 and 8443.

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 charts/. Which is also where all the subcharts such as the whoami resource will live.

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.

@99linesofcode
Copy link
Owner Author

99linesofcode commented Jun 25, 2025

Spinning up the cluster is now as simple as running helm install laravel-stack .. The whoami service can be reached at http://localhost once it is up and running.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants