release notes: 6.3.0 — add workload identity support#1042
Conversation
PR #508 (Feb 2026) added a cloud-neutral workload-identity hook to the service chart — top-level serviceAccount block (create, name, annotations) plus per-component extraPodLabels on agent, api, worker, logger, router, and delayedJobMonitor. The Azure storage backend gained DefaultAzureCredential fallback in the same PR; the S3 backend already supported keyless auth via boto3's default credential chain. End-to-end this enables: - Azure: AKS Workload Identity / Arc clusters via UAMI annotation + WI label - AWS: EKS IRSA / Pod Identity via role-arn annotation GCS/Swift/TOS backends still require static credentials — flagged as a caveat so users don't assume keyless works everywhere. These were in 6.3.0 code but missing from the release notes — adding a Highlights bullet and a detailed Helm Charts entry. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughAdds 6.3.0 release notes announcing workload identity support: a cloud-neutral ChangesWorkload Identity Release Notes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Description
PR #508 (merged Feb 24, 2026, before the 6.3.0 tag on Apr 27) added cloud-neutral workload-identity support to the service chart but never landed in the 6.3.0 release notes. This PR backfills two entries:
serviceAccountblock (create,name,annotations) and per-componentextraPodLabelsonagent,api,worker,logger,router, anddelayedJobMonitor. Includes the exact annotations/labels each CSP's webhook expects, and an explicit caveat that GCS/Swift/TOS backends still require static credentials (those backendsNotImplementedErroronDefaultDataCredentialin backends.py).The chart hooks themselves are cloud-neutral — the per-CSP differences (Azure needs both an SA annotation and a pod label; AWS only needs the SA annotation; the storage-backend side needs
DefaultAzureCredentialfor Azure but boto3's default credential chain handles IRSA on S3 without code changes) are documented as concrete examples rather than buried in prose.Doc-only change — no code or tests touched.
Issue #None
Checklist
🤖 Generated with Claude Code
Summary by CodeRabbit