Kubernetes is big, complicated, and complex. You don’t need it for home usage at all.
However, it has so much out of the box and extensions and extras to fit any organization.
Imagine you have to host thousands of containers to match your scale. Load balance across all of them, maintain hard tenant isolation, mTLS, observability, etc.
How do you manage if one service out of hundreds (or more) breaks? Should all services break? Some? Service mesh on k8s enables this.
If you tried to build a new k8s with feature parity, it would be just as complex.
I help organizations containerize and move onto k8s and regularly tell people it doesn’t make sense.
It also doesn’t make sense to jump directly to it unless your team already has experience.
Start with containers, either docker or podman. You’ll get surprisingly far with either.
Kubernetes is big, complicated, and complex. You don’t need it for home usage at all.
However, it has so much out of the box and extensions and extras to fit any organization.
Imagine you have to host thousands of containers to match your scale. Load balance across all of them, maintain hard tenant isolation, mTLS, observability, etc.
How do you manage if one service out of hundreds (or more) breaks? Should all services break? Some? Service mesh on k8s enables this.
If you tried to build a new k8s with feature parity, it would be just as complex.
I help organizations containerize and move onto k8s and regularly tell people it doesn’t make sense.
It also doesn’t make sense to jump directly to it unless your team already has experience.
Start with containers, either docker or podman. You’ll get surprisingly far with either.