So I have rebuilt my Production rack with very little in terms of an actual software plan.

I host mostly docker contained services (Forgejo, Ghost Blog, OpenWebUI, Outline) and I was previously hosting each one in their own Ubuntu Server VM on Proxmox thus defeating the purpose.

So I was going to run a VM on each of these Thinkcentres that worked as a Kubernetes Cluster and then ran everything on that. But that also feels silly since these PCs are already Clustered through Proxmox 9.

I was thinking about using LXC but part of the point of the Kubernetes cluster was to learn a new skill that might be useful in my career and I don’t know how this will work with Cloudflared Tunnels which is my preferred means of exposing services to the internet.

I’m willing to take a class or follow a whole bunch of “how-to” videos, but I’m a little frazzled on my options. Any suggestions are welcome.

  • non_burglar@lemmy.worldEnglish
    3·
    9 hours ago

    Running the k8s in their own VM will allow you to hedge against mistakes and keep some separation between infra and kube.

    I personally don’t use proxmox anymore, but I deploy with ansible and roles, not k8s anymore.

    • nagaram@startrek.websiteOPEnglish
      3·
      9 hours ago

      Ansible is next on my list of things to learn.

      I don’t think I’ll need to dedicate all of my compute space to K8s probably just half for now.

      • corsicanguppy@lemmy.caEnglish
        21·
        8 hours ago

        Ansible is next on my list of things to learn.

        Ansible is y2k tech brought to you in 2010. Its workarounds for its many problems bring problems of their own. I’d recommend mgmtconfig, but it’s a deep pool if you’re just getting into it. Try Chef(cinc.sh) or saltstack, but keep mgmtconfig on the radar when you want to switch from 2010 tech to 2020 tech.

        • kata1yst@sh.itjust.worksEnglish
          1·
          7 hours ago

          Wow, huge disagree on saltstack and chef being ahead of Ansible. I’ve used all 3 in production (and even Puppet) and watched Ansible absolutely surge onto the scene and displace everyone else in the enterprise space in a scant few years.

          Ansible is just so much lower overhead and so much easier to understand and make changes to. It’s dominating the configuration management space for a reason. And nearly all of the self hosted/homelab space is active in Ansible and have tons of well baked playbooks.