Tako Schotanus

> where he/she could add new labels using a pop-up list to specify to which resource the label should be then added Is that something we can expect the user...

Indeed, if OSIO for example removed "community" boosters and left only the "redhat" ones because the choice could confuse users then I think labels/annotations are a very advanced option. Not...

Ok, after way too much time spent debugging to figure out why labels were not being created I today encounter this issue: https://github.com/openshift/origin/issues/3819 Seems setting labels on projects/namespaces is not...

I'm testing an alternative way to set the labels. (Just in case the the other works takes longer than expected). Will let you know how it goes.

Nope, sorry, I don't know why/how it's possible to do so using the `oc` CLI command, but using `fabric8:kubernetes-client` I get: ``` Failure executing: PATCH at: https://192.168.42.42:8443/api/v1/namespaces/xxx. Message: User "developer"...

The OpenShift console itself already has this functionality, right? Just confirming that we want the same in the Launcher.

Ok, but images always come from a registry, right? AFAIK there's no (standardized) image file that you can create from a docker/buildah image, or is there?

@ALRubinger this might not be easy in all cases. Of the 4 backend runtimes only Vert.x [explicitly implements a health check](https://github.com/fabric8-launcher/launcher-creator-backend/blob/master/catalog/generators/platform-vertx/files/src/main/java/io/openshift/booster/MainApplication.java#L45). In the case of Node we might point to...

Also, wouldn't we need health check for the frontend too? If so how do we display that in the Welcome App? As two different cards, one for the frontend and...

@ALRubinger those images don't come from the redhat registry, they come from Docker Hub.