Package additonal RedHat Docker Images - Nexus, Gogs, Gerrit, Letchat

[cmoulliard]

In order to have the possibility to simplify the build, deployment & code review process (s2i, maven workflow), we should deploy the Nexus, Gerrit, Gogs, Letchat, sonarqube, ...CD/CI ... Kubernetes Api as RedHat Docker Images (Red Hat Customer Portal) within the PDK.

• Such images are maintained here : https://github.com/fabric8io?utf8=%E2%9C%93&query=docker
• Kubernetes App are maintained here : https://github.com/fabric8io/fabric8-devops`

[hferentschik]

Are you suggesting to pre-install/cache these images? We do this already for the base OSE images and the box file has already reached about 1 GB now.

So far I have not thought so much further than just the basic OpenShift installation, but of course adding these images is essential for the further evolution of the PDK.

[cmoulliard]

If we don't want to preinstall them, the user could use the gofabric8 tool to install the required images when required

[maxandersen]

@cmoulliard does gofabric8 use the productized versions or community bits ?

Where do we find the gofabric8 ?

btw. I don't think all these should be preloaded by default - we are already big. But yes, having a documented/supported and scriptable way to do it we should definitely have.

[cmoulliard]

@maxandersen here you can find gofabric8 : https://github.com/fabric8io/gofabric8

[hferentschik]

This really relates to #39. I think for now we should just make it easy to install fabric8 by provisioning gofabric8 on the VM

[maxandersen]

yeah, definitely should see if "just works".

[hferentschik]

I am going to test it :-)

[christian-posta]

@maxandersen gofabric8 can use whatever version we point it at, but AFAIK there are not productized releases of the CI/CD stuff from fabric8 /cc @cmoulliard ?

[cmoulliard]

This is really important and urgent that we have productized releases of the CI/CD stuffs like (jenkins, nexus, sonarqube, letschat, taiga, gogs, gitlab) otherwise that will be almost impossible to continue to promote RedHat CD/CI Strategy

[christian-posta]

+1 @cmoulliard we should take that internally to PM.

[rafaeltuelho]

I deployed fabric8 templates on my CDK using gofabric8 utility. But I observed that it creates/deploys a new docker registry (fabric8-docker-registry) for fabric8. I was wondering if it make sense, once CDK already has an internal registry.

How this works? Two docker registries inside the same cluster? Can someone explain me if it's the expected behaviour?