• 2 Posts
  • 33 Comments
Joined 11 months ago
cake
Cake day: September 4th, 2023

help-circle




  • I have a k3s cluster for fun and I can admit that k8s is way too complicated.

    I don’t want to dig hours through documentation to find what I’m looking for. The docs sometimes feel like they were written for software devs and you should figure part of the solution yourself.

    I have a ExternalName service that keeps fucking up my cluster everytime it restarts, bringing down my ingresses, because for some reason it doesn’t work and I have no idea where to look at to figure out why it doesn’t work - I just end up killing the service and reapplying the yaml file and it works.

    I had to diagnose why my SSL certificates would get stuck in “issuing” in cert-manager, had to dig through 4 or 5 different resources until I got to an actual, descriptive error message telling me that I configured my ClusterIssuer wrongly.

    I wanted a k3s cluster to learn but every time I have issues with it I realize it’s a terrible idea.

    I wish I had podman + compose but it does seem like a docker-compose is more complicated. Also, I wish I could do ansible but I have no idea where to start (nor how it works).

    EDIT: oh yeah I also lost IPv6 support because k3s by default doesn’t enable v6 and I was planning on using Hetzner CCM to have a 2 node cluster until I realized Hetzner Networks don’t support v6.















  • xinayder@infosec.pubtoSelfhosted@lemmy.worldNever Again
    link
    fedilink
    English
    arrow-up
    1
    ·
    5 months ago

    My issues with Samsung nowadays is that they offer a very low TBW warranty compared to other brands like Kingston.

    I wanted to buy a 1TB storage for my games and I couldn’t decide between Samsung and Kingston. Samsung had a 600TBW warranty for the 1TB model, Kingston had 800. I ended up choosing the KC3000 from Kingston.


  • That doesn’t seem to be the case. From what I read on HN, the dev quit because he thought it didn’t make sense to submit CVEs for temporary/wip solutions, and F5 thought otherwise.

    So as I see it, the developer quit because he didn’t agree that a CVE should be opened for a work-in-progress solution that was live on Nginx.