You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was advised to raise an issue regarding the possibility of bypassing the queue-proxy. Currently, I am migrating my service to Knative, and the configured proxy is Kourier. While I have external TLS in place, I am concerned about potential security risks associated with the HTTP connection between queue-proxy and Kservice. Can the queue-proxy get bypassed some way?
What version of Knative?
0.9.x
0.10.x
0.11.x
Output of git describe --dirty
Expected Behavior
Actual Behavior
Steps to Reproduce the Problem
The text was updated successfully, but these errors were encountered:
Hi @nardineshak, what are the security risks for the QP <-> APPs connection given that this is on local network within the pod? Are your refering to the end-to-end connection between activator and QP? We have implemented internal encryption for Kourier as well: https://knative.dev/docs/serving/encryption/encryption-overview. Would that help with the risks?
I was advised to raise an issue regarding the possibility of bypassing the queue-proxy.
Is there a discussion happening elsewhere upstream?
Can the queue-proxy get bypassed some way?
No, that is not an option.
cc @ReToCode who may have to add more on the topic.
I was advised to raise an issue regarding the possibility of bypassing the queue-proxy. Currently, I am migrating my service to Knative, and the configured proxy is Kourier. While I have external TLS in place, I am concerned about potential security risks associated with the HTTP connection between queue-proxy and Kservice. Can the queue-proxy get bypassed some way?
What version of Knative?
Expected Behavior
Actual Behavior
Steps to Reproduce the Problem
The text was updated successfully, but these errors were encountered: