You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to propose that kamel run is enhanced to be able to stop right before applying the k8s CRs that it generates - i.e. use the build kit to create the target image, push that image into the registry, create the k8s CRs (Deployment, Service, Route, etc), but don't apply them.
The main use case / requirement I am trying to solve is the performance of how quickly a Camel K Integration can come up. Let's say I have a fixed number of integrations and I want my clusters & integrations to come up as quickly as possible.
Thoughts?
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!
I would like to propose that
kamel run
is enhanced to be able to stop right before applying the k8s CRs that it generates - i.e. use the build kit to create the target image, push that image into the registry, create the k8s CRs (Deployment, Service, Route, etc), but don't apply them.The main use case / requirement I am trying to solve is the performance of how quickly a Camel K Integration can come up. Let's say I have a fixed number of integrations and I want my clusters & integrations to come up as quickly as possible.
Thoughts?
The text was updated successfully, but these errors were encountered: