News for hackers. Stuff that matters.
Re:Bare-Metal Kubernetes with K3s by ninjha on Tuesday December 22, 2020 @01:06PM (#25509213)
I’m working on this right now. My theory is that having every cluster object defined in git (but with clever use of third party helm charts to reduce maintenance burden) is the way to go.

Our cluster configuration is public[1] and I’m almost done with a blog post going over all the different choices you can make wrt the surrounding monitoring/etc infrastructure on a Kubernetes cluster.

[1] https://github.com/ocf/kubernetes

Re:Bare-Metal Kubernetes with K3s by nicolast on Tuesday December 22, 2020 @05:19PM (#25512008)
My comment above did not come out of the blue, but based on real-world experience ;-) You may be interested in our MetalK8s project [1] which seems related to yours.

[1] https://github.com/scality/metalk8s

Re:Bare-Metal Kubernetes with K3s by aprdm on Tuesday December 22, 2020 @05:37PM (#25512214)
This looks really cool. Would you include dev apps in the mono repo too? Say you have 40 services by 20 different teams.
Re:Bare-Metal Kubernetes with K3s by tutfbhuf on Wednesday December 23, 2020 @05:25AM (#25516234)
If I already have an production cluster up and running for a while, how can I get it git tracked now?

Another question: how about things like autoscaler which automatically edits numbers in deployments, how to git track that?