Tomas Kral

> @kadel - the auto generation of health checks are done using fabric8 maven plugin enrichers/generators, right now we have enrichers/generators for Spring Boot, Vert.x, Karaf, Web and Jar.. to...

My only concern here is what happens if we set wrong health check. The application won't run / will get killed just because Kedge Chose the wrong health check. If...

> Known issues with the demo video: if I re-build image then the latest image is not deployed by k8s. So in the doc we are creating we need to...

The most important part is what will be generated by `imageStream` shortcut. We need to clearly define that

shortcut ``` imageStream: foo:bar ``` should generate add this to deploymentConfg: ``` triggers: - type: "ImageChange" imageChangeParams: automatic: true from: kind: "ImageStreamTag" name: "foo:bar" containerNames: - "foo" ``` detecting and...

How you propose to do that? We can't use Deployments annotations/labels, as that will make it impossible to add Deployment specific labels without adding them to other objects. One way...

`name` is a bit different case, as it is a required field, it has to be set for every object, and it is just single value. `labels` and `annotations` are...

Golang example work in progress : https://github.com/kadel/golang-example/

While working on this I found a couple of OSIO issues: - https://github.com/openshiftio/openshift.io/issues/1300 - https://github.com/openshiftio/openshift.io/issues/1315 And fabric8-pipeline-library issue: - https://github.com/fabric8io/fabric8-pipeline-library/pull/360

After some troubles and with workarounds I have first working Pipeline for golang example (without Kedge) - https://github.com/kadel/golang-example