astefanutti commented on issue #2113: URL: https://github.com/apache/camel-k/issues/2113#issuecomment-811695328
@squakez yes the current default values match the community catalog that comes in OpenShift 4. Changing these would break people using the upstream CLI version with OpenShift 4. Another option would be to have _dynamic_ default values, as the `kamel install` command is capable of detecting the environment it's installing onto. If we were to keep _static_ default values, then we would have to assess what is the dominant usage to make a decision. I haven't seen any evidence that OLM on Kubernetes is taking off? Are there any major Kubernetes distribution, aside OpenShift, that comes with OLM OOTB? I'd be inclined to think the dominant OLM use case is on OpenShift, and that the upstream CLI install command should default to the community catalog, which is the case. For the product catalog in OpenShift 4, these variables are set as Go build-time variables in downstream builds, whose CLI binaries can be downloaded from the OpenShift Web console, which is the dominant use case for product versions. -- 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: us...@infra.apache.org
