4 ms·
but the situation could be the reverse: I replace someone who did a pile of k8s and didn't document anything, and while I could orchestrate the whole with libvi
by marmaduke 8y ago
but the situation could be the reverse: I replace someone who did a pile of k8s and didn't document anything, and while I could orchestrate the whole with libvirt recipes in my sleep, I wouldn't even know how to look up the command
> kubectl get pods --all-namespaces
so familiarity is not a good argument here
- ownagefool 8y agoTrue. In order to know kubernetes, you need to know kubernetes. But the point is at least it's a framework rather than someone you or I came up with and never wrote down. But if you don't know it, you don't know it. The question is, is learning it useful?
- mmt 8y ago> The question is, is learning it useful? Even that question is too broadly posed. The question is, is learning it in addition to[1] the previously-standard tools useful? [1] In the context of the article, this might be "instead of", which presents a much lower bar.
- rconti 8y agoI don't see how libvert is easier to learn than kubernetes. Neither one is obvious to a sysadmin who hasn't worked in either world.
- marmaduke 8y agoI meant that familiarity with a framework isn’t an argument. Libvirt isn’t doing exactly the same thing as k8s and it isn’t easier or harder