On 27/11/2019 04:49, Gorkem Ercan wrote:
> What exactly is the mechanics of the container merging? Is it
> something that plugin broker does?
My original idea was to merge everything that relies on the same image.
I don't know if that's a good way. I'm unfamiliar with the code that
constructs pods out of a devfile and can't really say what's best.
> Do we expect the extension developers to explicitly mark their
> extensions for container merging?
That really depends on what we want to achieve. If we're after reducing
the amount of containers we run (to improve sharing resources), we
should not expect that, if we just want to cover the case of jdt.ls, we
can require it. But even then, we need to match versions, etc.
I do not think we can get away from explicitly marking. We can introduce merging as an optimization measure but
we can not depend on container merging to solve the case of
jdt.ls. I think we need a way for extensions to say that
they depend on an extension (which they already do) and can live on its image.
/Thomas
