Now that we can run `kamel run runtime/examples/routes.js -w --logs`, I see that we create two pods each time we deploy a integration, not just one.
The output of each pod is prefixed with a progressive number in brackets (e.g. `[1]`): ``` integration "routes" created integration "routes" in phase Building integration "routes" in phase Deploying integration "routes" in phase Running [1] Monitoring pod routes-577bbd8f65-kl7mq[2] Monitoring pod routes-79c97fdbb-pxcnk[2] Starting the Java application using /opt/run-java/run-java.sh ... [2] exec java -javaagent:/opt/jolokia/jolokia.jar=config=/opt/jolokia/etc/jolokia.properties -javaagent:/opt/prometheus/jmx_prometheus_javaagent.jar=9779:/opt/prometheus/prometheus-config.yml -XX:+UseParallelGC -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -XX:MinHeapFreeRatio=20 -XX:MaxHeapFreeRatio=40 -XX:+ExitOnOutOfMemoryError -cp .:/deployments/* org.apache.camel.k.jvm.Application [1] Starting the Java application using /opt/run-java/run-java.sh ... [1] exec java -javaagent:/opt/jolokia/jolokia.jar=config=/opt/jolokia/etc/jolokia.properties -javaagent:/opt/prometheus/jmx_prometheus_javaagent.jar=9779:/opt/prometheus/prometheus-config.yml -XX:+UseParallelGC -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -XX:MinHeapFreeRatio=20 -XX:MaxHeapFreeRatio=40 -XX:+ExitOnOutOfMemoryError -cp .:/deployments/* org.apache.camel.k.jvm.Application [1] I> No access restrictor found, access to any MBean is allowed ``` [ Full content available at: https://github.com/apache/camel-k/issues/90 ] This message was relayed via gitbox.apache.org for [email protected]
