Antonin Stefanutti

Cross-namespace IntegrationKit references are already supported in the Integration type, so that seems like a reasonable request to surface it into the CLI.

> Thanks a lot. The point is when the Operator has been installed with the `--global` option, let's say in namespace `camel-k` and we're going to create an integration in...

Thanks for raising it. JDK is required by the JOOR compiler, that compiles the Java routes at start time. It should be possible to use a JRE-only base image when...

@SubhasmitaSw I can see two possible work-around that I'd like to be confirmed: * Copy the `script/Makefile` into the project root directory and try to run from there * Overwrite...

@SubhasmitaSw great, assigned :)

@SubhasmitaSw I've updated the issue title and description. Let me know if that's correct.

> @astefanutti Yes, It looks good now. One things, is this still to be considered a `good-first-issue`? @SubhasmitaSw I was inclined to be optimistic, but I infer from your comment...

Yes it seems KEDA also requires the `.spec.replicas` to be set. Some context has been shared in https://github.com/apache/camel-k/pull/2838#discussion_r783859878. I agree, the `.spec` block should not be updated by the operator....

> For many cases defaulting to `.spec.replicas=1` seems to make sense. What if we set up `.spec.replicas` on an integration only when Knative profile is not chosen, or Knative Service...

When using Camel K, maybe even the entire integration platform should be deleted and cascade delete the integration contexts and the integrations.