zhiminglim edited a comment on issue #2756: URL: https://github.com/apache/camel-k/issues/2756#issuecomment-972966527
Thank you for your reply! I have patched the camel k operator deployment env with your solution, it is working now and suppressing the kamelets installation when i create an IntegrationPlatform in other namespaces. A question on this: if I'm using Camel K 1.6.0, is this the only way to go about setting that env variable? Also, I noticed that a CamelCatalog CR is also created when I create the IntegrationPlatform via helm, and it remains in the namespace when I remove the IntegrationPlatform. Is there also a way to clean this up? The reason for these questions, and us not using the Kamel CLI uninstall option, is because we use Camel K CRDs (such as IntegrationPlatform and Integration) within a helm chart for our integration use cases. Hence when I uninstall the helm chart, I would like to clean up the Kamelets and CamelCatalog which are created as a by-product by the camel k operator. Edit: Have performed upgrade of Camel K Operator to 1.7.0, hence the question has been answered. -- 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
