• 2 Posts
  • 42 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle

  • And Alpine, the one @Sxan started with.

    Alpine has apk, and is (or it should be) the most used base for container images. It is very small, smaller than Debian, so containers built on it are secure and performant.

    If you’ve never worked with Docker/Podman/OCI containers, you’ve been missing a lot of good stuff, and you may have heard of Alpine via the amazing “I use Linux as my operating system” copypasta:


    “I use Linux as my operating system,” I state proudly to the unkempt, bearded man. He swivels around in his desk chair with a devilish gleam in his eyes, ready to mansplain with extreme precision. “Actually”, he says with a grin, "Linux is just the kernel. You use GNU+Linux!’ I don’t miss a beat and reply with a smirk, “I use Alpine, a distro that doesn’t include the GNU Coreutils, or any other GNU code. It’s Linux, but it’s not GNU+Linux.” The smile quickly drops from the man’s face. His body begins convulsing and he foams at the mouth and drops to the floor with a sickly thud. As he writhes around he screams “I-IT WAS COMPILED WITH GCC! THAT MEANS IT’S STILL GNU!” Coolly, I reply “If windows were compiled with GCC, would that make it GNU?” I interrupt his response with “-and work is being made on the kernel to make it more compiler-agnostic. Even if you were correct, you won’t be for long.” With a sickly wheeze, the last of the man’s life is ejected from his body. He lies on the floor, cold and limp. I’ve womansplained him to death.





  • The problem with non-PLP drives is that Rook-Ceph will insist that its writes get done in a way that is safe wrt power loss.

    For regular consumer drives, that means it has to wait for the cache to be flushed, which takes aaaages (milliseconds!!) and that can cause all kinds of issues. PLP drives have a cache that is safe in the event of power loss, and thus Rook-Ceph is happy to write to cache and consider the operation done.

    Again, 1Gb network is not a big deal, not using PLP drives could cause issues.

    If you don’t need volsync and don’t need ReadWriteMany, just use Longhorn with its builtin backup system and call it a day.


  • F04118F@feddit.nltoSelfhosted@lemmy.worldKubernetes storage backends
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    3 months ago

    I tried Longhorn, and ended up concluding that it would not work reliably with Volsync. Volsync (for automatic volume restore on cluster rebuild) is a must for me.

    I plan on installing Rook-Ceph. I’m also on 1Gb/s network, so it won’t be fast, but many fellow K8s home opsers are confident it will work.

    Rook-ceph does need SSDs with Power Loss Protection (PLP), or it will get extremelly slow (latency). Bandwidth is not as much of an issue. Find some used Samsung PM or SM models, they aren’t expensive.

    Longhorn isn’t fussy about consumer SSDs and has its own built-in backup system. It’s not good at ReadWriteMany volumes, but it sounds like you won’t need ReadWriteMany. I suggest you don’t bother with Rook-Ceph yet, as it’s very complex.

    Also, join the Home Operations community if you have a Discord account, it’s full of k8s homelabbers.






  • The way I understand it, there’s 2 use cases for a VPN, with different concerns and providers:

    • having access to your private home network from anywhere, through an encrypted tunnel (Tailscale, Wireguard on the router, etc)
    • having your outgoing traffic to the internet go through an anonymized exit node so that your ISP can not watch or sell what you are doing (ProtonVPN, Mullvad VPN, etc)

    Is Tailscale fit for the second? I thought not, as the exit node is not an anonymized VPN server but one of your own machines.