[
https://issues.apache.org/jira/browse/CAMEL-21238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883000#comment-17883000
]
Thomas Diesler commented on CAMEL-21238:
----------------------------------------
I fixed a few issues with reexport that prevented re-deploy. Now, re-deploy
starts, but there is an issue with the shutdown hook and re-capturing the
output of the new k8s process. Currently (as you say), there is no in-container
hot swap of camel resources in a running container (as we had in camel-k) and
given all complexities and even the questionable idea of swapping stuff in an
otherwise immutable container, I'd prefer the cleaner route of re-export +
re-deploy.
>From the usage perspective, it is ...
ctrl+c
camel k8s run ...
stopping the container removes the k8s resources (because of cleanup with --dev)
camel k8s run, is the re-export + re-deploy
yes, I really think that there is little benefit and lots of potential headache
with hot swapping resources (i.e. what if I want to change two files)
> camel-jbang - k8s run - Reloading project does not change route behaviour
> -------------------------------------------------------------------------
>
> Key: CAMEL-21238
> URL: https://issues.apache.org/jira/browse/CAMEL-21238
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Priority: Major
> Fix For: 4.9.0
>
>
> When running a project with `--dev` like this ...
> {code}
> jbang camel kubernetes run timer-log-route.yaml --logs --dev \
> --gav=examples:timer-log:1.0.0 \
> --trait container.imagePullPolicy=IfNotPresent \
> --trait service.type=NodePort \
> --runtime=quarkus
> {code}
> I see ...
> {code}
> Reloading project due to file change: timer-log-route.yaml
> {code}
> without image re-build/deploy
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
