Document KYA use case for agent client authorization on envoy AI GW#193
Merged
Conversation
Add a use case for a VC/KYA based dynamically scoped, fine grained/TBAC for Agents on AI gateway Signed-off-by: Manish Singh <mksinghtx@gmail.com>
mksinghtx
requested review from
beryder,
copasseron,
hmuyal,
jadiaconu,
mayannuz,
mkedjour and
rafaelsilva29
as code owners
mksinghtx
changed the title
This use case can work with both KYA and VC Signed-off-by: Manish Singh <mksinghtx@gmail.com>
Updated description for use case using KYA or VC
mkedjour
approved these changes
Apr 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a use case for a VC/KYA based dynamically scoped, fine grained/TBAC for Agents on AI gateway
Description
Please provide a meaningful description of what this change will do, or is for.
Bonus points for including links to related issues, other PRs, or technical
references.
Note that by not including a description, you are asking reviewers to do extra
work to understand the context of this change, which may lead to your PR taking
much longer to review, or result in it not being reviewed at all.
Type of Change
Checklist