Shared Storage V2: Write rendered data to Kubernetes Secrets
Open
@shobham-nv is already working on this.
Since Jul 15, 2026.
- Dominant language
- Go
- Stars
- 218
- Forks
- 72
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 427
Description
Description
Add an ESS Agent template sink that writes rendered sensitive data to a configured key in an existing Kubernetes Secret instead of a filesystem destination.
Requirements
- Parse
k8s_secret { name namespace key }. - Reject templates that set both
destinationandk8s_secret. - Use the in-cluster Kubernetes client to patch only the owned
data[key]. - Enforce the 768 KiB decoded per-key and 900 KiB decoded total-data limits.
- Preserve unchanged-value no-op behavior and return clear errors for NotFound, Forbidden, and retryable API failures.
Definition of Done
- Tests cover configuration validation, patch behavior, unchanged values, size limits, and API errors.
- Unrelated Secret keys remain unchanged.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.