nicolaferraro opened a new issue #1897: URL: https://github.com/apache/camel-k/issues/1897
With 1.3.0, doing: ``` kamel install ```` Creates a default catalog: ``` kubectl get camelcatalog NAME RUNTIME VERSION RUNTIME PROVIDER camel-catalog-1.6.0 1.6.0 quarkus ``` But when an integration is run: ``` kamel run examples/Sample.java -w ``` Then another catalog is created. ``` kubectl get camelcatalog NAME RUNTIME VERSION RUNTIME PROVIDER camel-catalog-1.6.0 1.6.0 quarkus camel-catalog-1.6.0-quarkus 1.6.0 quarkus ``` The `-quarkus` catalog is created because a mechanism exists that creates a catalog when one is not available for the platform runtime. We have only 1 runtime now, but anyway a new catalog is created and the default one ignored. At a first glance, the reason seems to be that the default catalog is missing the `camel.apache.org/runtime.provider: quarkus` annotation. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
