Camel K doesn't support kubernetes services of type loadbalancer

[pabloxtiyo]

Hi Guys, do you know how to change/modify the service that camel k creates by default from ClusterIp to LoadBalancer?
im running this command::
kamel run StackDriverWebHookRoute.java --dependency=camel-rest --dependency=camel-restlet -n arch --dev

but service is always a ClusterIp

[astefanutti]

Thanks for the feedback. There is currently no option to set the service type, hence defaulting to ClusterIP, though it should be straightforward to add an option to the service trait.

[github-actions]

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

[sschere]

I've faced the same issue, and solved by creating an adicional service as LoadBalancer. Let's say your service deployed using kamel run is being called "rest-dsl", then below kubectl cli will create a new service called "rest-dsl-lb". Then you can keep kamel deploying into a NodePort type and the LoadBalancer will redirect to that. I hope that helps:

kubectl expose service rest-dsl --name rest-dsl-lb --port=80 --type=LoadBalancer --target-port=8080

[github-actions]

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

[tadayosi]

Right now Service trait only has NodePort bool flag but we should introduce a new property Type that accepts ClusterIP, NodePort, and LoadBalancer and deprecate the NodePort bool flag.

[essobedo]

Should be fixed by #3618