squakez commented on issue #3964: URL: https://github.com/apache/camel-k/issues/3964#issuecomment-1411796060
> @squakez I have just a few questions about `we should aim to make Camel K the deployment tool for Kubernetes Camel applications`. Camel application is just a common Java application with Camel libraries in it. The mostly used Camel Runtimes: Quarkus and SpringBoot. > > 1. Quarkus has its own extension for deployment > > 2. SpringBoot usually used with jkube > > > Why do we need to develop a Camel specific deployment tool? What value does it bring to developers? I think that, beside simplifying the deployment model (from a simple route deep down the whole Kubernetes world of configuration to tune), Camel K add a series of operational aspects, such as monitoring, scaling, etc, that may be possible without CK, but definitely more difficult to achieve. The main values I can list on top of my head for Camel K are: - Automating the parsing of a route and composing a project with all required components/dependencies (still room for improvement here, and likely we'll join the Camel JBang to fully achieve it as stated in 2023 roadmap) - Inherit previous Camel K kit containers and reduce the time to build/run an application - Manage the container registry on behalf of the user - First class citizen for Serverless in conjunction with KNative - Enable a managed service model and/or an EDA via Kamelet/KameletBinding - Promote a Camel application across environments - Injecting resources (properties, configmaps, ...) to be used easily from the route - Fine tune Kubernetes with simple traits (ie, you don't have to create a `Service` if the route expose an http port) - Simplify the upgrade process when a new Camel version is available I guess I forget something. In general I think that, although a Camel application may look like any other Java application, in reality, there are more opinionated aspects typical of a framework that Camel K manage for the user. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
