[
https://issues.apache.org/jira/browse/CAMEL-21238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882980#comment-17882980
]
Thomas Diesler commented on CAMEL-21238:
----------------------------------------
I'd say there is little benefit in k8s reload. AFAICS, it would do the same as
stopping/deleting the current container (ctrl+c) followed by k8s run.
Can we remove the reload functionality from KubernetesRun?
> 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)
