Wire AllowedAudiences from AgentRuntime CRD to AuthProxy sidecar

[akram]

Summary

• Adds spec.identity.allowedAudiences field to the AgentRuntime CRD, allowing per-agent JWT audience overrides
• Wires the field through AgentRuntimeOverrides → ResolvedConfig → per-agent ConfigMap generation
• Injects allowed_audiences into the pipeline.inbound.plugins[jwt-validation].config section of the per-agent ConfigMap
• Transitional mechanism to support application-to-agent flows (e.g. playground → agent) until the auth model is finalized

Example usage

apiVersion: agent.kagenti.dev/v1alpha1
kind: AgentRuntime
metadata:
  name: my-agent-runtime
spec:
  type: agent
  targetRef:
    apiVersion: apps/v1
    kind: Deployment
    name: my-agent
  identity:
    allowedAudiences:
      - playground
      - kagenti-agents

Changed files

File	Change
api/v1alpha1/agentruntime_types.go	Add AllowedAudiences []string to IdentitySpec
internal/webhook/injector/agentruntime_config.go	Extract from CR, add to AgentRuntimeOverrides
internal/webhook/injector/resolved_config.go	Add to ResolvedConfig, merge with AR precedence
internal/webhook/injector/pod_mutator.go	injectAllowedAudiences() helper, pass through both call sites
internal/webhook/injector/pod_mutator_test.go	Tests for injection and nil cases
api/v1alpha1/zz_generated.deepcopy.go	Regenerated
config/crd/bases/agent.kagenti.dev_agentruntimes.yaml	Regenerated CRD manifest

Closes #368

Test plan

• Unit tests pass (go test ./internal/webhook/injector/...)
• Verified on OpenShift (ROSA) with redbank-demo-test-envoy namespace:
  • Patched AgentRuntime CRs with allowedAudiences: ["redbank-demo-test-envoy", "account"]
  • Confirmed allowed_audiences appears in per-agent ConfigMaps under pipeline.inbound.plugins[jwt-validation].config
  • Confirmed authbridge sidecar starts and accepts user tokens with matching audiences (inbound authorized)
  • Full E2E: playground → orchestrator → banking/knowledge agents working with envoy-sidecar mode
• Negative test: agents without allowedAudiences in CR have no allowed_audiences in ConfigMap

🤖 Generated with Claude Code

[huang195]

Adds spec.identity.allowedAudiences []string to the AgentRuntime CRD and wires it through to the per-agent authbridge ConfigMap's pipeline.inbound.plugins[jwt-validation].config.allowed_audiences. Closes #368. Both proxy-sidecar and envoy-sidecar code paths thread an allowedAudiences parameter through ensurePerAgentConfigMap. Two new tests cover AR-set-injects and nil-doesn't-inject.

Areas reviewed: Go (CRD type, deepcopy, override extraction, ResolvedConfig, pod mutator, tests), kubebuilder annotations, kagenti commit/PR conventions
Commits: 1, signed-off (DCO passing)
CI status: 14/15 passing; E2E pending

Three meta-level items, easy to apply before merge:

1. Commit-message attribution: trailer uses Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>. Kagenti convention (root CLAUDE.md "Commit Attribution Policy" + the ai-assisted-by-trailer pre-commit hook) is Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com>. The pre-commit hook should have rewritten this — worth checking whether it ran. git rebase --signoff + manual edit fixes it.

2. PR body footer: reads 🤖 Generated with [Claude Code](https://claude.com/claude-code). Same kagenti convention applies (root CLAUDE.md "PR Bodies" section): footer should be Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com>, not "Generated with". One-line edit to the PR description.

3. PR title: no emoji prefix. Kagenti repo:pr convention is <emoji> <Short descriptive title> — feat: would be replaced by ✨ (or add ✨ as a prefix to the existing title). Not blocking.

Four inline comments below — one suggestion (dead code in ResolvedConfig), three nits / suggestions for hardening.

Verdict: APPROVE — feature works as advertised, dead-code finding (the inline #1 below) doesn't block merge but is worth cleaning up in a follow-up so future engineers don't reasonably assume ResolvedConfig.AllowedAudiences is the canonical source of truth.

[huang195]

@akram please rebase and resolve conflict?

[akram]

@akram please rebase and resolve conflict?

done (rebased and solved conflicts), and review's comments have been addressed