Skip to content
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

Way to Bypass Queue-Proxy #15632

Open
nardineshak opened this issue Nov 27, 2024 · 1 comment
Open

Way to Bypass Queue-Proxy #15632

nardineshak opened this issue Nov 27, 2024 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@nardineshak
Copy link

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

@nardineshak nardineshak added the kind/bug Categorizes issue or PR as related to a bug. label Nov 27, 2024
@skonto
Copy link
Contributor

skonto commented Nov 28, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants