Roland Huß
Roland Huß
@jimmidyson Why not ? At least when building and pushing stuff with the maven plugin you are going through the docker daemon directly. If you would know the container id...
ok, understand. What about the idea of an exec-proxy service like with https://github.com/taskcluster/docker-exec-websocket-server ?
just brainstorming ;-), but yeah, something like that. Isn't the node a pod is running on retrievable ? But even then you are right, how to start the proxy on...
@rawlingsj As the console tries to reach the Jolokia agent here via the pod (?) ip from the browser, this obviously doesn't work. The connection should go over the API...
Sorry I have no fabric8 installation right now to test or to debug (and unfortunately not much resources left to help much). What are the steps I would need to...
I just sent a PR as https://github.com/fabric8io/fabric8-ipaas/pull/581 to disable the openshift authentication in which case we should be good again. For testing fabric8/message-broker:2.2.168-1 and fabric8/message-gateway:2.2.168-1 has been pushed to docker...
@rawlingsj feel free to review and trigger a release if happy.
> @iocanel When renaming, can we move the orga/groupId, too ? For fmp and dmp we are considering to move away from fabric8, so this would be a good occassion...
> LGTM. Will the `groupId` change too? Yes, I would recommend this as fabric8 turns out to be kind of a burned name (as least according to my latest survey)....
> Now, I haven't considered groupId change, org change, or anything. My proposal had more to do with renaming the repository and changing the way we commicate the project. But...