The Docker images are complex for the sake of the Helm charts, which sometimes need to pass down tons of parameters

These aren't just for your laptop, they're supposed to be able to run in prod

I'm still stuck with 3 bitnami charts that I keep updated by building from source, which includes also building the images, all on our private registry.

▲

mrweasel 5 days ago | parent [-]

That makes some sense. I've only used Bitnami images with Docker compose or as standalone containers. In those case you're frequently better of just mounting in a configuration file, but that won't really work in Kubernetes.

I would argue that if you run Kubernetes, then you frequently already have the resource to maintain your own images.

	▲	raziel2p 5 days ago \| parent \| next [-]
		You'd also have to maintain the helm chart, which is arguably far more work. If you don't need the bitnami helm chart functionality, using more stock container images is easy and preferable.
	▲	wink 5 days ago \| parent \| prev [-]
		I had not used bitnami images for.. probably 5 years at this point and they always seemed servicable in a pinch, usually used for testing and I when I brought this up recently I was also told (by k8s users) that the helm stuff is probably what actually has most people up in arms because it is very common. We're the minority who remember bitnami as a non-critical choice among many.