I'm liking the look of devopskube; its also very similar to fabric8 ;). BTW the home page says:

fabric8 - highly based on RedHats OpenShift, probably the closest to our requirements

fabric8 is actually totally based on kubernetes. It works great on vanilla kubernetes, minikubehttps://fabric8.io/guide/getStarted/gofabric8.html, GKE or you can spin fabric8 up on stackpoint - we just make sure that stuff works on kubernetes and openshift.

We've got helm 2 charts for all the microservices in fabric8, together with a single chart for the fabric8 platform - though that chart has an issue I hope to have fixed quite soon ;) - until then we recommend just using the single yaml file instead (or gofabric8 start).

So I'd love to learn more about why you didn't think fabric8 was right for you & to see if we could work closer together.

e.g. we've almost got single sign on with keycloak going for the console, jenkins and gitlab. We've been using Jenkins + kubernetes + nexus for quite a while now and been through many iterations of plugins/approaches and have now got to a pretty good place using the kubernetes-plugin defining build pods in the Jenkinsfile using @Library to refer to a pipeline library; then using a PVC to mount local maven repo, share secrets and so forth.

Whatever happens, good luck - but I hope we can work more closely together & share code/work/microservices where possible