#1283: Enhance the kamel log command to show more detail prior to i…

[phantomjinx]

…nstall

• Sets up a polling prior to the complete install of an integration
• First report whether it finds the integration
• Assume it finds an integration then determine its status
• If it gets to Building Kit (which can take a while) then find the
  associated IntegrationKit and report its status
• Finally return to the scraping of the log once the integration is up
  and running

Release Note

NONE

[nicolaferraro]

Thanks @phantomjinx, having more info really helps.

I've not tested it, but I see there's some code reporting the state of the integration kit. There is already some info about that, because Kubernetes events are also printed.

Have you checked this when installing the operator + running kamel with a admin user (an user that can manage Kubernetes events), to see if there's some duplication.

This of course should work with any kind of users.

[phantomjinx]

Thanks @phantomjinx, having more info really helps.

I've not tested it, but I see there's some code reporting the state of the integration kit. There is already some info about that, because Kubernetes events are also printed.

Have you checked this when installing the operator + running kamel with a admin user (an user that can manage Kubernetes events), to see if there's some duplication.

Hey @nicolaferraro

Been developering & running this through as cluster-admin. The events for the integration-kit are more detailed in that they include information of conditions and scaling up. The reason I include mention of the integration-kit in the kamel log is due to the Build Running phase of the integration taking the bulk of the time. Without mention of the integration-kit, the integration log just sits there for 2-3 minutes. Anyway, this is an example of kamel log sample:

⌁66% [: … camel-k] master(1) 130 ± kamel log sample
Integration 'sample' not yet available. Will keep checking ...
The building kit for integration 'sample' is at: Build Submitted
The building kit for integration 'sample' is at: Build Running
Integration 'sample' is at: Deploying ...
Integration 'sample' is now running. Showing log ...
[1] Monitoring pod sample-746854ccb4-5zgct
[1] exec java -cp ./resources:/etc/camel/conf:/etc/camel/resources:/etc/camel/sources/i-source-000:dependencies/camel-k-integration-1.3.0-SNAPSHOT-runner.jar:dependencies/io.quarkus.arc.arc-1.8.0.Final.jar:dependencies/io.quarkus.quarkus-arc-1.8.0.Final.jar:dependencies/io.quarkus.quarkus-bootstrap-runner-1.8.0.Final.jar:dependencies/io.quarkus.quarkus-core-1.8.0.Final.jar:dependencies/io.quarkus.quarkus-development-mode-spi-1.8.0.Final.jar:dependencies/io.quarkus.quarkus-ide-l
....

Let me know if you think it needs tuning further.

[nicolaferraro]

Cool!