Azure Blob as a storage backend
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
Start by reviewing Cachew's existing S3 support and the backend interfaces referenced in the issue. Clarify whether Azure Blob should support both cache and shared metadata backends, which credential mechanisms and consistency requirements apply, and whether maintainers approve the design before defining implementation work.
Written by the indexing model from the issue text.
Description
Background
We are interested in running Cachew in Azure environments where Azure Blob Storage is the preferred shared object store.
Cachew currently supports S3 for remote cache and metadata storage. We would like to understand whether the project would be open to adding native Azure Blob Storage support for:
- A cache backend.
- A metadata backend shared across Cachew replicas.
A possible configuration could look like:
azure-blob {
account-url = "https://account.blob.core.windows.net"
}
cache azure-blob {
container = "cachew"
max-ttl = "8h"
}
metadata azure-blob {
container = "cachew"
}
Authentication would use the standard Azure SDK credential mechanisms, with connection-string support for local development and testing.
Before preparing a contribution, we would appreciate feedback on:
- Whether native Azure Blob Storage support fits the project's direction.
- Whether both cache and metadata backends would be welcome.
- Any preferred design constraints or consistency requirements.
- Whether this should use the existing backend interfaces directly or follow another planned storage abstraction.
If the maintainers are open to this, we can prepare a more detailed proposal and implementation.
- Dominant language
- Go
- Stars
- 41
- Forks
- 14
- Avg merge
- 23h 22m
- Merged PRs (30d)
- 2
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.
More from block/cachew
-
etag-range-followup
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
-
Difficulty 4/5 3-5 days Newbie friendliness 56/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·