[GitHub] [camel-k] davesargrad edited a comment on issue #1232: Camel-K Doesn't Create a Service or Ingress for an Integration

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

davesargrad edited a comment on issue #1232: Camel-K Doesn't Create a Service or Ingress for an Integration
URL: https://github.com/apache/camel-k/issues/1232#issuecomment-579803305
 
 
   @jamesnetherton Good feedback. It strikes me that what you suggest is a good solution,  unless the integration is parameterized in a fashion that prevents the ingress URL from being specified in the URI. In this case, I'd think that the camel-k integration builder should still be able to create the service. I wonder if the camel-k team has plans to support adding the component the way that @rndIndy has. It seems like that should have worked. @nicolaferraro Do you have some thoughts on whether or not there are plans to support expanded methods for auto-creating the required services. Also is there a plan to support service types other than ClusterIP? For example, I'd think that it would be useful to create LoadBalancer or NodePort services at times.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services