Che registries (plugin+devfile) should be part of Che deployment

[l0rd]

By default Che plugin and Che devfile registries should be deployed along with the wsmaster. This is mainly needed to make sure that the version of the wsmaster and the version of those registries are always consistent. A user should still be able to use an already deployed registry but the default should be do deploy a new instance (as per keycloak and postgres for multi-user Che).

Sub tasks:

• Update Che Helm Chart Update Che Helm Chart: Che registries (plugin+devfile) should be part of Che deployment #13633
• Update Che Operator Che registries (plugin+devfile) should be part of Che operator deployment redhat-developer/rh-che#1476
• Add the registries in Che release process (build and tag nightly and release images) Need to release registries (devfile + plugin) automatically via dedicated centos ci job #13953

[l0rd]

cc @slemeur @nickboldt @rhopp

[tsmaeder]

So the idea is to have a registry for "latest", one for "next", etc.?

[l0rd]

@tsmaeder nightly, latest, 7.0.0, 7.1.0 etc...

[skabashnyuk]

AFAIK last time we think about such kind of issue was minimum memory requirements to start che locally. Is this something that is no longer in our list?

[skabashnyuk]

@l0rd can you confirm that increased memory requirement ~500m for local development are acceptable and expected.

[l0rd]

Do we need 250MB per registry? Can set required memory to 50MB?

…

[skabashnyuk]

Don't know yet, we can try. Not sure about 50mb may be 100mb.

[sparkoo]

From @metlos's experiments, 16MB is minimum to run registry without performance drop. He tested with 1000 sequential requests.
I've set memoryLimit: 32Miand memoryRequests: 16Mi in #13890.