• 2 Posts
  • 20 Comments
Joined 1 year 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
    ·
    8 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.







  • Thanks for the suggestions!

    I ended up configuring my CI pipeline to build a Caddy docker image that ships with my website files. The pipeline is also publishing the container image to the Codeberg registry and I apply the new image repo and tag to the Caddy Helm chart I found on ArtifactHub.

    The only thing that’s left is to setup the CI to automatically restart the pod when a new image is pushed, so it will always have the latest version.

    It was easier than expected and I had a few issues like my stylesheets not being applied and image files not rendering, but it was solved by changing the pathType field on the ingress configuration to Prefix.






  • I’m not using k8s just to host my website, I have other services on it as well.

    I know it’s overkill for small stuff, but I’m running k3s and not k8s (so it’s a lightweight engine). The reason I’m doing this is for learning purposes, I want to learn more about k8s and thought I could do an experiment with it on a VPS.

    I plan on renting another VPS and adding another node to the cluster, as it’s pretty cheap (Hetzner ARM server costs around 3.8 EUR without VAT with 2 vCPUs and 4GB RAM). For example, it’s much more cheaper than the VPS I have on Vultr that has 1GB RAM and 1 vCPU.