scrubbles

...SQL?

Butthurt we respect women or something I suspect

Everyone here saying confidently "no" hasn't kept track of science over the last several thousand years. There have been hundreds/thousands of things that have been "that is impossible" that we simply didn't have the knowledge for to be able to do.

200 years ago you would have been laughed at for thinking man could ever take to the skies, and now flying is a boring tedious thing for us.

75 years ago the idea of carrying a computer in your pocket with thousands of times the sum of the entire compute availability in the world back then would have been scoffed at, and people would have told you it's impossible. Now we use it to post on forums like this like it's nothing.

Both are examples of "it's impossible, the science says so", but that's the neat thing about science. We learn new things every day. Our thoughts change, you don't "believe" in science, you only learn new things.

So is it impossible? I think it's incredibly small-minded and dare I even say arrogant to say it's impossible. How do we know what will be discovered tomorrow, or 100 years from now, or 1000 years from now? We have absolutely no idea what will be possible then. With our current technology? Absolutely not. In 400 years? Who knows someone may be standing in line at security and see a meme making fun of us for thinking it was impossible.

Do we have a release date yet for the US?

Yours for only 4 easy payments of 39.95! (Plus shipping and handling)

If you're only at 2 nodes, then I think host paths with node selectors are what you should go with. That gets you up and running in the short term, but know that the conversion later to something like Longhorn will be a process. (Creating the volumes, then copying all the data over, ensuring correct user access, etc).

So you have a classic issue of datastorage on kubernetes. By design, kubernetes is node-agnostic, you simply have a pile of compute resources available. By using your external hard drive you've introduced something that must be connected to that node, declaring that your pod must run there and only there, because it's the only place where your external is attached.

So you have some decisions to make.

First, if you want to just get it started, you can do a hostPath volume. In your volumes block you have:

volumes:
  - name: immich-volume
    hostPath:
      path: /mnt/k3s/immich-media # or whatever your path is

The gotcha is that you can only ever run that pod on the node with that drive attached, so you need a selector on the pod spec.
You'll need to label your node with something like kubectl label $yourNodeName anylabelname=true, like kubectl label $yourNodeName localDisk=true Then you can apply a selector to your pod like:

    spec:
      nodeSelector:
        localDisk=true

This gets you going, but remember you're limited to one node whenever you want data storage.

For multi-node and true clusters, you need to think about your storage needs. You will have some storage that should be local, like databases and configs. Typically you want those on the local disk attached to the node. Then you may have other media, like large files that are rarely accessed. For this you may want them on a NAS or on a file server. Think about how your data will be laid out, then think about how you may want to grow with it.

For local data like databases/configs, once you are at 3 nodes, your best bet with k3s is Longhorn. It is a HUGE learning curve, and you will screw up multiple times as a warning, but it's the best option for managing tiny (<10GB) drives that are spread across your nodes. It manages provisioning and making sure that your pods can access the volumes underneath, without you managing nodes specifically. It's the best way to abstract away not only compute, but also storage.

For larger files like media and linux ISOs, then really the best option is NFS or block storage like MinIO. You'll want a completely separate data storage layer that hosts large files, and then following a guide like this you can enable mounting of NFS shares directly into your pods. This also abstracts away storage, you don't care what node your pod is running on, just that it connects to this store and has these files available.

I won't lie, it's a huge project. It took about 3 months of tinkering for me to get to a semi-stable state, simply because it's such a huge jump in infrastructure, but it's 100% worth it.

I was a hardcore Thomas the tank engine nerd.

And Theodore Tugboat.

Seems a bit opposite of the whole "innocent until proven guilty" thing

Helm has worked well for me, what's the problem you had?

This is why I like the manifold method, but you can get creative by combining splitters.

Remember that things are equally split. Need 1/3 here and 2/3 there? One output goes here, Merge two outputs of a splitter to go there. Need more complicated fractions? Expand the math to allow more

They have proven over and over that consumer brands aren't anything to them. They constantly chase flashy buzzwords and quarterly earnings over improving and fixing their longstanding issues