Summary
kagenti-extensions#356 added AllowedAudiences support in the AuthProxy sidecar, including the aud[] array parsing fix. However, there is currently no way to configure AllowedAudiences declaratively via the AgentRuntime CR — the operator doesn't know about this field yet.
This issue tracks the work to expose AllowedAudiences through the operator so that it can be set via the CRD and passed to the AuthProxy sidecar configuration.
What needs to happen
- Add an
allowedAudiences field to the AgentRuntime CRD spec (e.g. under spec.auth)
- Wire that field through the operator's reconciliation logic so it gets passed to the AuthProxy sidecar configuration
Context
AllowedAudiences is considered a transitional/bridge mechanism until the auth model is finalized (see discussion thread)
- Related bug issue: kagenti-extensions#406 — AuthProxy should support the
aud[] claim included in inbound JWT
- Without this operator change, there is no declarative way for users to configure which audiences the AuthProxy should accept, which blocks the application-to-agent flow
References
Summary
kagenti-extensions#356 added
AllowedAudiencessupport in the AuthProxy sidecar, including theaud[]array parsing fix. However, there is currently no way to configureAllowedAudiencesdeclaratively via theAgentRuntimeCR — the operator doesn't know about this field yet.This issue tracks the work to expose
AllowedAudiencesthrough the operator so that it can be set via the CRD and passed to the AuthProxy sidecar configuration.What needs to happen
allowedAudiencesfield to theAgentRuntimeCRD spec (e.g. underspec.auth)Context
AllowedAudiencesis considered a transitional/bridge mechanism until the auth model is finalized (see discussion thread)aud[]claim included in inbound JWTReferences