Split Operator binary from Kamel CLI binary

[squakez]

Right now we use kamel binary as both the operator binary to be executed on the Pod and as the CLI we ship to final user. Although the size of the file is not yet too big (around 30 MB), I think we could benefit from having 2 separate binaries, the CLI to be shipped to the users and the operator to be bundled into the container image.

Reactions?

[oscerd]

Frankly, at this stage, I don't see a good reason for doing it.

[squakez]

Thanks @oscerd. Just to complete the quick description above, the idea would not to break the project in separate subprojects, but have the same release cycle and procedure. The only thing is that we will build 2 deliverables which serve different concerns.

[github-actions]

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!

[tadayosi]

Removing the stale label as it still seems to be worth exploring.

[squakez]

@tadayosi , FYI, you can also add status/never-stale in order to avoid it become stale again in the future.

[squakez]

Implicitly included in the will to move part of the CLI running logic into Camel JBang. Closing.