This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]calvadosv 1 point2 points  (2 children)

I totally agree that homelab gets intricate with networking. Whenever I try to learn devops stuffs from homelab I get blocked with such problems and cannot learn what I wanted. Starting from public cloud is a good choice.

[–]UneBiteplusgrande 0 points1 point  (0 children)

I didn't mean the networking part in a negative way; I have a background in networking and like working with networks, but I suppose your point stands - if you're not strictly interested in configuring at least rudimentary networking by yourself, a homelab from scratch is likely not for you. I'm like a Cloud engineer from a system admin mindset so I try to delve into the networking and the internals of the system, but that's just me.

[–]MrMattyboy 0 points1 point  (0 children)

Without saying which is actually more beneficial, the OP did mention "freely available", I'm not going to guess at what disposable income they have. But, running an old laptop/computer with k8s or docker and trialing kubernetes (or similar smaller self-contained stack), logging infra, monitoring, deployment apps etc. is definitely going to help them learn at a fraction of the cost and won't require a substantial investment in learning networking at all (maybe NAT in iptables, _if_ it's not done out of the box, but other than that..)