I've spent a bunch of time doing little things in Kubernetes and Docker, but I think I have to start eating my own dogfood here and living in Kubernetes a bit -- doing things I depend on to experience the full range of things that using the Orchestration enviroment does well, and seeing what I have gaps in.

I'd also like to spend some time on past vulnerabilities, and maybe even spin a vulnerable version up (with limited outside visibility) to have some chances to play with stuff.

Okay, so there is a plan. Now, how to action it? First thing is to leverage Kubernetes natural strength, and build some bits that launch a website. I want to divide this in half, with one set of bits that builds the Infra bits and another set of bits to build the web bits with the latest web changes. If I do it right, I think I could end up with a single deployable image composed from a multipart build.

Now this can be just a demo so far, but once I've got that working there is a build area that I'm doing now that's a good candidate. Right now I have some manual process to build the infra then tar.gz filed or similar that are the "builds", and it might be nice if we moved to a CI/CD system or at least some reproducable scripts. From there, I'd like to experiment with things like APIs, running non-http services like SMTP and once I get that in a happy spot maybe fiddle with VoIP. Along the way, I'd like to figure out logs/observability and better understand K8s networking.

I haven't talked enough about migrating some of my existing websites, but getting even dev/test versions in to such a system will help me a lot, and can let me decide if I want to make the leap on other bits as well. It will hopefully shift my overall cloud facing strategy, and move to more of an IaC -- Infrastructure as Code -- mindset. And changing strategies adds tactics to the toolset and hopefully some agility and speed.