jlh

joined 2 years ago
[–] jlh@lemmy.jlh.name 2 points 3 weeks ago

Ah cool, I'll check it out.

[–] jlh@lemmy.jlh.name 9 points 3 weeks ago (3 children)

The home manager documentation bothers me a lot

[–] jlh@lemmy.jlh.name 6 points 3 weeks ago* (last edited 3 weeks ago)

Probably not that hard to build a simple flask frontend around it.

Automatically processing files in an S3/WebDAV directory would also be useful.

[–] jlh@lemmy.jlh.name 1 points 3 weeks ago

https://docs.k3s.io/installation/uninstall

There is also a k3s option for Nixos, which removes the security and side-affect risks of running a random bash script installer.

[–] jlh@lemmy.jlh.name 9 points 3 weeks ago

Definitely so in the EU

[–] jlh@lemmy.jlh.name 2 points 3 weeks ago

Spread the word!

[–] jlh@lemmy.jlh.name 5 points 3 weeks ago

Very true. Each brick you lay upgrades your setup and your skillset. There are very few mistakes in Kubernetes as long as you make sure your state is backed up.

[–] jlh@lemmy.jlh.name 2 points 3 weeks ago* (last edited 3 weeks ago)

For question 1: You can have multiple resource objects in a single file, each resource object just needs to be separated by ---. The small resource definitions help keep things organized when you're working with dozens of precisely configured services. It's a lot more readable than the other solutions out there.

For question 2, unfortunately Docker Compose is much more common than Kubernetes. There are definitely some apps that provide kubernetes documentation, especially Kubernetes operators and enterprise stuff, but Docker-Compose definitely has bigger market share for self-hosted apps. You'll have to get experienced with turning a docker compose example into deployment+service+pvc.

Kubernetes does take a lot of the headaches out of managing self-hosted clusters though. The self-healing, smart networking, and batteries-included operators for reverse-proxy/database/ACME all save so much hassle and maintenance. Definitely Install ingress-nginx, cert-manager, ArgoCD, and CNPG (in order of difficulty).

Try to write yaml resources yourself instead of fiddling with Helm values.yaml. Usually the developer experience is MUCH nicer.

Feel free to take inspiration/copy from my 500+ container cluster: https://codeberg.org/jlh/h5b/src/branch/main/argo

In my repo, custom_applications are directories with hand-written/copy-pasted yaml files auto-synced via ArgoCD Operator, while external_applications are helm installations, managed via ArgoCD Operator Applications.

[–] jlh@lemmy.jlh.name 2 points 3 weeks ago (1 children)

helm charts are awful, i didn't really like cdk8s either tbh. I think the future "package format" might be operators or Crossplane Composite Resources

[–] jlh@lemmy.jlh.name 9 points 3 weeks ago

Just do that 10,000 times over 300,000 years and you'll have as much as Bazy Boy

[–] jlh@lemmy.jlh.name 7 points 4 weeks ago* (last edited 4 weeks ago)

Excuse you, I don't have a problem.

[–] jlh@lemmy.jlh.name 2 points 4 weeks ago (1 children)

There's much better algorithmic and datatype optimizations to be made than to design your app around saving 3 bytes that most runtimes probably represent as a long long anyways

view more: ‹ prev next ›