[
https://issues.apache.org/jira/browse/CAMEL-21238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882686#comment-17882686
]
Claus Ibsen commented on CAMEL-21238:
-------------------------------------
Okay so reloading locally is to let quarkus trigger reloading in the same JVM
where source files are updated and its out of the box in quarkus.
Reloading in k8s can be
* same as local, need to sync source code from camel-jbang user to running k8s
container in the right folder.
* do a container rebuild and restart the container
And we can argue whether reload (dev mode) in k8s run should be supported or
not.
> 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)
