Skip to content

docs: hip for s3 storage #395

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: hip for s3 storage #395

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
31 changes: 31 additions & 0 deletions hips/hip-9876.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
---
hip: "9876"
title: "S3 storage"
authors: [ "Kamil Krzywicki <[email protected]>", "Björn Wenzel" ]
created: "2025-04-08"
type: "feature"
status: "draft"
helm-version: "4"
---

## Abstract

Store helm release data in S3-compatible storage.

## Motivation

Helm release secrets can be pretty huge if release that is managed by them is big as well (long yamls/json/properties for applications). This makes our etcd storage quite big as well and this causes increased costs to handle bigger etcd nodes.

## Rationale

There is an alternatve to default storage in kubernetes secrets there is database storage. But this seems to be an overkill to store simple data like helm releases with all the maintenance costs for running database with HA.
That's why something simple, highly available and popular like S3 (compatible) storage should be a perfect match.
Alternative could be pluggable storage for helm, but S3-comapatible storage seems to be very popular and could be introduced in the base helm binary.
Copy link

@TerryHowe TerryHowe May 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think a better solution here is make some small changes to the OCI client to read files instead of registries in OCI layout format.

See https://oras.land/blog/lightweight-cloud-registry-oras/


## Backwards Compatibility

No backwards compatibility issues

## Reference Implementation

Reference implementation was submitted in this [PR](https://github.com/helm/helm/pull/12173).