[GitHub] [camel-k] tadayosi commented on issue #3849: Create normal service when knative-service trait is disabled

[GitBox <gi...@apache.org>]

tadayosi commented on issue #3849:
URL: https://github.com/apache/camel-k/issues/3849#issuecomment-1328603571

   It's related to how the profile is detected for an integration. Whenever you have Knative serving in the cluster, integrations are by default resolved to `Knative` profile. And Service trait is enabled only when the profile is either `Kubernetes` or `OpenShift`.
   
   You should be able to fix the issue by explicitly assign one of them for an integration instead of letting it unspecified in an env where Knative serving is installed already.
   
   So I think the questions are two-fold:
   
   1. Does it make sense to disable Knative Service trait under `Knatvie` profile?  And does it make sense to create a service when the profile is `Knative`?
   2. Should we improve the current profile detection logic?  If yes, how?
       https://github.com/apache/camel-k/blob/v1.10.3/pkg/controller/integration/platform_setup.go#L68-L89


-- 
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-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org