Myasnikov Daniil 5fb337de19 fix(harbor): guard registry-s3 render against partial BucketInfo ...

The COSI BucketAccess controller is expected to populate `BucketInfo`
atomically, but the prior guard (`with .Values.spec` / `with .secretS3`)
only short-circuits on missing or empty inputs. A partially populated
`secretS3` would still emit the registry-s3 Secret with empty
`accessSecretKey`/`endpoint` values, and a missing `bucketName` was
not guarded at all — silently breaking Harbor's S3 storage backend.

Tighten the inner guard to require all four required fields
(accessKeyID, accessSecretKey, endpoint, bucketName) before the Secret
is emitted, so partial input falls into the no-render path alongside
unset/empty. The body now uses dot-access on `.secretS3` for
consistency with the new gate. Behaviour for fully populated input is
unchanged.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>

2026-04-30 16:40:15 +05:00

..

bucket-secret.yaml

fix(harbor): guard registry-s3 render against partial BucketInfo

2026-04-30 16:40:15 +05:00

database.yaml

Fix system postgresql images to 17.7-standard-trixie

2026-04-10 12:47:46 +05:00

redis.yaml

fix(harbor): resolve Redis nil pointer on first install

2026-02-18 00:50:12 +03:00