-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Leverage platform http service in camel-knative #264
Labels
enhancement
New feature or request
Comments
/cc @nicolaferraro |
lburgazzoli
added a commit
to lburgazzoli/apache-camel-k-runtime
that referenced
this issue
Mar 19, 2020
lburgazzoli
added
enhancement
New feature or request
and removed
question
Further information is requested
labels
Mar 20, 2020
lburgazzoli
added a commit
to lburgazzoli/apache-camel-k-runtime
that referenced
this issue
Mar 20, 2020
lburgazzoli
added a commit
to lburgazzoli/apache-camel-k-runtime
that referenced
this issue
Mar 20, 2020
lburgazzoli
added a commit
to lburgazzoli/apache-camel-k-runtime
that referenced
this issue
Mar 20, 2020
lburgazzoli
added a commit
to lburgazzoli/apache-camel-k-runtime
that referenced
this issue
Mar 23, 2020
lburgazzoli
added a commit
that referenced
this issue
Mar 24, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As today camel-knative comes with its own web-server as we designed the component to be as flexible as possible so we allow to expose knative service to different ports.
This flexibility is proven not to be very useful so I'd propose to remove such flexibility and when possible, to leverage the http service provided by the platform.
The text was updated successfully, but these errors were encountered: