issue #311 - shifting to kamel log instead of kubectl log

[bfitzpat]

Signed-off-by: bfitzpat@redhat.com bfitzpat@redhat.com

[bfitzpat]

Switching to kamel log [integration] instead of kubectl logs-f [podname] gives us uninterrupted coverage of the running integration, including when the integration is re-deployed with changes. The issue was that using kubectl required us to follow a single pod, which is then discarded when an integration is re-published. The kamel version follows the integration through shutting down a running pod and spinning a new one up.

The only problem I have found is a complete lack of log feedback when the kit is created and the pod is first spinning up. There is just... nothing. Without any kind of user feedback, some users may wonder if the integration will ever spin up.

I have asked for an update in apache/camel-k#1283 so that the user can see something moving while waiting for the integration to start. Running kamel log [integration] at the command line has the same problem.

[apupier]

works great.

I have some questions that I put in comment.

(I miss test :'-()