lburgazzoli commented on issue #3964: URL: https://github.com/apache/camel-k/issues/3964#issuecomment-1413323580
> > * Let Camel K operator be able to manage also any kind of Camel deployments (also traditional CSB/CQE - for example via label selectors). Can be done later in 2.x. > > I like this idea, too. [hawtio-online](https://github.com/hawtio/hawtio-online) has been providing such feature on K8s/OpenShift, but it requires a Camel application to be Jolokia-enabled. I'm interested in how much functionality can be transferred from hawtio-online to the Camel K operator. I think the main advantage are: - discoverability (no need to scrape pods and container port, just look at integration CR) - the status reporting of an Integration can include information for tooling (management consoles, cli, etc) to access the management interface - tools (management consoles, cli, etc) can use the integration' status reporting to provide information about the status of the integration without having to deal with internals of camel (i.e. scraping pods health check probes) which greatly reduces grants required by 3th party applications and avoid doing the same thing on a number of tools. - camel-k operator can set-up the integration automatically to enable secure access to the management endpoint (SSL, AuthN, AuthZ, etc) - would make kubectl a first class citizen for camel k operations Unrelated to camel-k, I think we can try to make the new camel-console the way to interact with camel leveraging i.e. [spring boot actuators](https://docs.spring.io/spring-boot/docs/current/reference/html/actuator.html) and future [dedicated management support in quarkus](https://docs.spring.io/spring-boot/docs/current/reference/html/actuator.html) to expose such functionality and get rid of JMX (at least as the protocol to interact with the running instances). -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
