Skip to content

docs(chart): note Pod Identity support rests on the aws-creds fork pin #5281

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.

Sign up for GitHub

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

Closed
Chessing234 wants to merge 1 commit into from
+9 −0
Closed

docs(chart): note Pod Identity support rests on the aws-creds fork pin #5281

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions deploy/charts/buzz/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -227,6 +227,15 @@ Save these. Losing any of them is data loss. See NOTES.txt printed by `helm inst
- **Cosign signing of the published chart** is a follow-up (the relay image is
attested via `actions/attest-build-provenance`; the chart is not yet). The
chart itself is published to GHCR — see [Releasing](#releasing).
- **EKS Pod Identity / IRSA support rests on a temporary `aws-creds` fork pin.**
The relay resolves S3 credentials from the pod IAM role only because the
workspace pins `aws-creds` to a fork (Cargo.toml `[patch.crates-io]`) that
adopts the aws-creds portion of durch/rust-s3#449 — the crates.io release
cannot read EKS Pod Identity credentials
(`AWS_CONTAINER_CREDENTIALS_FULL_URI` + `AWS_CONTAINER_AUTHORIZATION_TOKEN_FILE`).
The pin reverts to crates.io once #449 lands upstream; until then, Pod Identity
support depends on an unmerged fork, so operators relying on it should track
that upstream issue.

## Releasing

Expand Down