> This goes strongly against the spirit of self-hosting where you know what you're running and you see the steps and all the integrations that are needed, including any reliance on third-party services that may come back to bite you.
No it doesn't. Just read the Dockerfile, it's self documenting and contains all the build steps.
Most of the time a Dockerfile is a very useful living installation reference documentation, but it's not guaranteed. It's entirely possible to encounter a Dockerfile that's just copying in binaries built outside of Docker or was a published image capture of hand installed stuff that is just being referenced in downstream images.
Parking permits in Montreal require you to have a home in the neighborhood you wish to park in. So this won't affect homeless people as they aren't parking there to begin with.
you might be fooled by the meaning of the word „distribution“ in the kubernetes vs. linux context.
in the linux context, a distribution would be an opinionated build of user-land tools around the linux kernel which might also bring patches done to the kernel by the distributor.
in the (cloud) kubernetes context, a distribution would be an opinionated (cloud) implementation of core kubernetes binaries (EKS/AKS/etc.pp.) on top of a linux-distribution of your liking.
to my humble understanding k3s is a stripped down and optimized (IMHO opinionated) build of kubernetes binaries derived from the official source.
kubeadm is the official projects (opinionated?) idea of arriving at a vanilla cluster, leaving you with the freedom to make choices for lots of the needed components involved.
in the linux context, „linux from scratch“ would be an analogy I suppose.
more knowledgeable people should please correct me if I‘m wrong in my understanding here.
No it doesn't. Just read the Dockerfile, it's self documenting and contains all the build steps.