[stokedbits]

Personally after using docker compose since it came out I’m excited to see the evolution of local Kubernetes development. I’d scrap even dealing with trying to make something as limited as docker compose do what you want. I’d focus on moving towards local Kubernetes development.

This will bring you closer to the deployment stack if you are deploying to Kubernetes. Then also let you leverage tools like kustomize to dry out your configurations.

There are some great projects like tilt, devspace, skaffold, etc that help facilitate deving on a local or remote cluster.

As far as configuration management that can be as simple as cascading kustomize configs or helm. Then leveraging something like vault. The point really is, if you start with Kubernetes you have way more flexibility with tooling and options to do whatever the heck you want.

Shameless plug I recently started a series on local Kubernetes development. It covers some of this with tilt and more. If you would like a specific thing covered here I can add an installment to it. https://youtube.com/watch?v=Nj55RDVwrIE&si=EnSIkaIECMiOmarE

[ecuaflo]

Thank you! Will you go on to teach infrastructure provisioning/IaC, CI/CD, live schema migrations, rollbacks, etc on a cloud provider with this stack? I would find the complete devops pipeline so helpful

[stokedbits]

Absolutely, that’s the ultimate goal and those are great ideas. Thanks for the feedback.

Right now I’m just getting my calibrations on learning how to make consumable content. I’ll be upgrading my setup soon to produce higher quality videos thanks to some friends donating some gear to me.

I’ll probably continue out a few more concepts here specifically to local development with this series. Then move on to a new project from start to finish. Maybe like a basic web app game or something that requires common infrastructure. I want to get more feedback data then make something really awesome once I get my bearings.

Right now I’d I were to do a stack it would be with what I’m familiar with. That would be IAC with something like terraform/cloudformation/CDK, then keep it simple with GitHub actions for CI/CD, go into migration/rollbacks/chaos/secops scenarios, and most likely deploy on both AWS (what I’ve used primarily for professional production) and digital ocean for my hobby projects.

[ditsuke]

This might end up being my gateway to learning and using k8s. Thank you!

[stokedbits]

You got it! I’m serious about feedback, so please post anything that you think might be helpful on the YouTube comments or on the GitHub repository. I’m doing this with the sole purpose to help people and learn how to be a better teacher :)