-
Notifications
You must be signed in to change notification settings - Fork 83
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
HTTP Endpoint for KOURIER_EXTAUTHZ_HOST #754
Comments
/good-first-issue We did not have the plan as nobody requested the feature. But I think it makes sense and complicated change is not necessary. PR is welcome 🙏 |
@nak3: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Thank you @nak3. I'll try to understand the code. According to the Envoy docs either grpc_service (config.core.v3.GrpcService) or http_service (extensions.filters.http.ext_authz.v3.HttpService) should be set. So I'm assuming there's also going to be some changes here? I'm very new to this, and barely getting around Knative, Kourier and GoLang. So forgive me if I'm not very helpful. |
Yes, I think you are right. Thank you! |
I see in the e2e tests for external authz that a gRPC service is supported. Any idea this will support a HTTP service?
I'd like to use ORY Oathkeeper as the external authenticator and it only exposes an HTTP endpoint for now.
The text was updated successfully, but these errors were encountered: