Skip to content

Commit adb9989

Browse files
authored
docs(harbor): document S3 object-storage (SeaweedFS) prerequisite (#2818)
2 parents c3a50d6 + 6cfa1a6 commit adb9989

1 file changed

Lines changed: 12 additions & 0 deletions

File tree

‎packages/apps/harbor/README.md‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,18 @@
22

33
Harbor is an open-source trusted cloud-native registry project that stores, signs, and scans content.
44

5+
## Prerequisites
6+
7+
The Cozystack Harbor app stores its registry data exclusively in S3-compatible object storage: the chart pins the registry backend to S3 and exposes no filesystem option. That bucket is provisioned through COSI (`objectstorage.k8s.io`) from a SeaweedFS deployment, so before deploying Harbor the tenant must have SeaweedFS available — enabled on the same tenant or inherited from a parent tenant (the resolved class is propagated down the tenant tree, surfaced as the `namespace.cozystack.io/seaweedfs` namespace annotation).
8+
9+
Enable it by setting `seaweedfs: true` on the tenant (or a parent tenant):
10+
11+
```yaml
12+
seaweedfs: true
13+
```
14+
15+
Without object storage in the tenant chain, Harbor cannot provision its registry bucket: the `<release>-registry` `BucketClaim`/`BucketAccess` never produces the `<release>-registry-bucket` credentials secret, so the Harbor `HelmRelease` stays unreconciled, waiting on `BucketInfo`.
16+
517
> `storageClass` is annotated as immutable in the chart schema — see [`docs/storage-immutability.md`](../../../docs/storage-immutability.md) for the contract and which consumers enforce it.
618

719
## Parameters

0 commit comments

Comments
 (0)