mobusta's recent activity
-
Comment on What programming/technical projects have you been working on? in ~comp
-
Comment on What programming/technical projects have you been working on? in ~comp
mobusta LinkCurrently we're deploying k3s at work. Right now I'm setting up my dev cluster - 1 control-plane, 3 worker nodes, 2 storage nodes for longhorn. I'm using kube-vip + traefik for lb and reverse...Currently we're deploying k3s at work. Right now I'm setting up my dev cluster - 1 control-plane, 3 worker nodes, 2 storage nodes for longhorn.
I'm using kube-vip + traefik for lb and reverse proxy. I had longhorn deployed but this was using the default root disk on the storage nodes so I'm re-configuring them to use a dedicated disk on each system for storage.
A lot of the work I'm doing is proof of concept / eval to show my team so we can do planning for what production will be like. Namely how we need to change our deployment pipeline since we want to use argocd + rollouts (with analysis in the future)
I still have spare nodes available so I might do a Talos deployment using metallb and nginx since I've seen people have opinions on k3s for production use. Thankfully we're a small team with a small user base internally for our applications so I don't think there's a wrong answer to this as before, we used docker swarm and it was fine.
Currently phasing out our docker swarm cluster for kubernetes. Right now we're moving our development deployments to kubernetes to test things out for now.
So far, the changes are holding. Code commits spool up drone, a secondary pipeline stage kicks off to update the manifest with the updated image tag thanks to kustomize, argocd picks up the change and a new replicaset gets created.
I will need to look into a way to template our manifests so I can more easily generate them for our deployments because copy/pasting and making slight adjustments to a dozen or so files is error prone.