Home Infrastructure as Code - Revisit (Part Two)

Change of plans…

With the plans for Red Hat to discontinue CentOS 8. I have decided to re-visit my design for this project and scrap most of the work I had done - I will share details on some of work in the future, such as my Packer pipeline.

A result of this is I have been able to simplify a large portion of my stack. For my current needs, I will initially only be setting up the following components.

• Proxmox
• K3OS
• Flux

One of the benefits of this setup is that it’s much easier to get started. This also means that I won’t lose focus and end up with multiple unfinished components (as was previously the case).

Additional problems to solve

Although my inital infrastructure is a lot simpler, I still have the following problems to solve.

• How do I gain remote access to the services in this cluster?
• How do I store my custom helm charts?
• How do I manage persistent volumes?

I intend to update this list as I come across additional problems and for each problem I should have a documented solution.