These days, people solve similar problems by wrapping their data in an OCI container image and distribute it through one of the container registries that do not have a practically meaningful pull rate limit. Not really a joke, unfortunately.

▲

mystifyingpoi 6 hours ago | parent [-]

Even Amazon encourages this, probably not intentionally, more like as a bandaid for bad EKS config that people can do by mistake, but still - you can pull 5 terabytes from ECR for free under their free tier each month.

	▲	XorNot 4 hours ago \| parent [-]
		I'd say it'd just Kubernetes in general should've shipped with a storage engine and an installation mechanism. It's a very hacky feeling addon that RKE2 has a distributed internal registry if you enable it and use it in a very specific way. For the rate at which people love just shipping a Helm chart, it's actually absurdly hard to ship a self contained installation without just trying to hit internet resources.