Aleksei Sviridkin caf4645cf2 docs(harbor): fix SeaweedFS discovery key described as annotation ...

The prerequisites section described the resolved SeaweedFS class as being
surfaced on the tenant namespace as the `namespace.cozystack.io/seaweedfs`
annotation. The tenant chart renders that key under `metadata.labels`,
alongside the sibling `/etcd`, `/ingress`, `/gateway`, `/monitoring` and
`/host` keys; no annotation of that name exists.

The wrong noun sends an operator to the wrong field. When a Harbor release
stays unreconciled waiting on `BucketInfo`, the documented check is to
confirm the tenant chain resolved a SeaweedFS class. Looking for it in
`.metadata.annotations` returns nothing even on a correctly configured
tenant, which invites the wrong conclusion that the tenant chain is broken
and sends the investigation away from the actual cause.

Signed-off-by: Aleksei Sviridkin <f@lex.la>

2026-07-14 13:45:19 +03:00

..

apps

docs(harbor): fix SeaweedFS discovery key described as annotation

2026-07-14 13:45:19 +03:00

core

test(e2e): migrate app suite from BATS to Chainsaw and wire into CI (#2826)

2026-07-12 11:58:08 +05:00

extra

fix(monitoring): surface missing VictoriaLogs and gate dead-end vlinsert ExternalName (#3215)

2026-07-09 01:55:01 +03:00

library

fix(cozy-lib,harbor,mariadb): digest-pin cleanup-hook kubectl image and route it through cozy-lib.images-registry

2026-07-02 17:44:59 +03:00

system

fix(fluxcd): omit empty distribution.artifact in FluxInstance for guest clusters (#3284)

2026-07-14 13:18:29 +03:00

tests/cozy-lib-tests

feat(cozy-lib): add CA-only TLS trust-anchor helper for tenants

2026-06-23 03:12:17 +03:00