-
Notifications
You must be signed in to change notification settings - Fork 4
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
TLS/HTTPS sink is unable to receive events #52
Comments
How does the Service look like? Isn't the Service the place to do SSL/TLS termination? |
indeed, service is only 80/8080 will take a look |
here is the PR for my cert manage work: knative/eventing#8385 |
The Camel-Quarkus container seems to listen on
Not sure what's the config to get it to listen on 8443, and mount in the certs from cert manager ? 🤔 |
I will have a look |
@matzew it should be enough to add these two EnvVars on the IntegrationSink:
More options (e.g. using .jks keystore, specifying a cert reload period) can be seen here: https://quarkus.io/guides/http-reference#configuring-the-http-server-directly With these options Camel Quarkus should listen on both ports 8080 and 8443. You can disable the Http port with
|
@christophd are the
are these generated, when doing the suggested ENV_VARs? I am still not abe to get this working. Here is my deployment, with additional mounts and those evn-vars:
and the mount is here, on the pod/deployment
and yes, quarkus is booting on both: 8080 / 8443:
|
a curl to |
@matzew Did you add the 443 -> 8443 port to the Service? |
damn!
that fixed it :-) |
Running with TLS, on the
IntegrationSink
there is a timeout on sending events to the Sink. Here is a log for a "source dispatcher", in a test suite:The log of the container looks like:
and the deployment for it is like:
The text was updated successfully, but these errors were encountered: