fluxCD brings a really nice helm-controller that will allow to change manifests via a postRenderers stub while still allowing to use regular helm tooling against the cluster.
https://fluxcd.io/flux/components/helm/helmreleases/#post-re...
I heard that argument before. Legitimizing one‘s own drug abuse for „medical reasons“ to make it socially acceptable.
Everyone is on some kind of spectrum and both people I had arguments with about your point of view - are both dead now thanks to overdosing.
I think the medical profession has a reason to exist and I‘d rather see people using professionals to treat their conditions than self-experimenting with possible fatal substances.
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.