| |
| ▲ | pclmulqdq 5 hours ago | parent [-] | | The complexity of k8s comes the moment you need to hold state of some kind. Now instead of one systemd entry, we have to worry about persistent volume claims and other such nonsense. When you are doing things that are completely stateless, it's simpler than systemd. | | |
| ▲ | p_l 4 hours ago | parent [-] | | If you need to care about state with systemd you still have the "nonsense" of persistent volume claims, they are just something you keep in notes somewhere, in my experience usually in heads of the sysadmins or an excel sheet or a text file that tries to track which server has what data connected how. | | |
| ▲ | pclmulqdq 3 hours ago | parent [-] | | Understand that in the hypothetical system we are discussing, there are something like 1-2 servers. In that case the "volume claim" is just "it's a file on the obvious filesystem" and does not actually need to be spelled out they way you need to spell it out in k8s. The file path you give in environment variables is where the most up-to-date version of the volume claim is. And that file is free to expand to hundreds of GB without bothering you. | | |
| ▲ | p_l 3 hours ago | parent [-] | | Things get iffier when you start doing things like running multiple instances of something (maybe you're sticking two test environments for your developers), or suddenly you grew a bit or no longer fit on the server and start migrating around. The complexity of PVCs in my experience isn't really that big compared to this, possibly lower, and I did stuff both ways. |
|
|
|
|
