-
Notifications
You must be signed in to change notification settings - Fork 29
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
[v0.14] Enable forwarding Authorization header in InferenceGraphs #467
[v0.14] Enable forwarding Authorization header in InferenceGraphs #467
Conversation
This will configure all `InferenceGraph` workloads to forward the standard HTTP `Authorization` header to the backing `InferenceServices`. The `Authorization` header is used to receive/send credentials and let ODH stack to validate access. By enabling forwarding of the `Authorization` header, we cover the case when there is an (some) auth-protected InferenceService(s) as part of an InferenceGraph. Access is fine-grained, so access to an InferenceGraph does not guarantee access to some InferenceService. The user needs to provide credentials to all resources (IGs and ISVC) that the request needs to go through. Since each workload validates credentials on its own, credentials need to be forwarded to all workloads of an InferenceGraph. Signed-off-by: Edgar Hernández <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: israel-hdez The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
"cpuLimit": "1", | ||
"headers": { | ||
"propagate": [ | ||
"Authorization" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Jooho @danielezonca Please, advice if this is fine.
I don't see an issue as long as everything runs over TLS.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is a good idea to add token to downstream endpoints.
|
/lgtm |
bce3a4e
into
opendatahub-io:release-v0.14
…b-io#467) This will configure all `InferenceGraph` workloads to forward the standard HTTP `Authorization` header to the backing `InferenceServices`. The `Authorization` header is used to receive/send credentials and let ODH stack to validate access. By enabling forwarding of the `Authorization` header, we cover the case when there is an (some) auth-protected InferenceService(s) as part of an InferenceGraph. Access is fine-grained, so access to an InferenceGraph does not guarantee access to some InferenceService. The user needs to provide credentials to all resources (IGs and ISVC) that the request needs to go through. Since each workload validates credentials on its own, credentials need to be forwarded to all workloads of an InferenceGraph. Signed-off-by: Edgar Hernández <[email protected]>
What this PR does / why we need it:
This will configure all
InferenceGraph
workloads to forward the standard HTTPAuthorization
header to the backingInferenceServices
.The
Authorization
header is used to receive/send credentials and let ODH stack to validate access.By enabling forwarding of the
Authorization
header, we cover the case when there is an (some) auth-protected InferenceService(s) as part of an InferenceGraph. Access is fine-grained, so access to an InferenceGraph does not guarantee access to some InferenceService. The user needs to provide credentials to all resources (IGs and ISVC) that the request needs to go through. Since each workload validates credentials on its own, credentials need to be forwarded to all workloads of an InferenceGraph.Which issue(s) this PR fixes
Fixes https://issues.redhat.com/browse/RHOAIENG-17827
Type of changes
Please delete options that are not relevant.
Feature/Issue validation/testing:
Checklist: