Open ThomasWollmann opened 5 years ago
I don't think that we actually need separate compose and kubernetes images, all orchestrator systems should be able to operate with the same set of very granular images. So I would go for "Fat" and "orchestrated". But yes, having separated repos facilitates release life-cycles in my view.
I agree with the naming.
Wouldn't it make more sense to have separate repositories for these two deployment strategies? Maybe we can add crosslinks to the repos for Fat/Compose/Kubernetes/... so people can easily decide at which scale they want to deploy Galaxy with Docker.