Aleksei Sviridkin 82e10878be fix(harbor): guarantee CPU for redis sentinels ...

The inline RedisFailover ran its three sentinels at 50m CPU request and
a 100m limit. Sentinels only become Ready after the redis-operator
elects a master and rewrites their monitored-master config, and on a
CPU-contended node CFS shares cycles proportionally to the request, so
underprovisioned sentinels converge slowly and delay harbor readiness
behind them. Raise the sentinels to Guaranteed QoS (requests equal
limits, 250m CPU / 128Mi) so election is never starved or throttled
under load. The redis data container is unchanged.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>

2026-07-27 22:48:24 +03:00

..

charts/harbor

feat(harbor): bump chart to 1.19.1 (Harbor 2.15.1)

2026-06-22 10:57:27 +03:00

templates

fix(harbor): guarantee CPU for redis sentinels

2026-07-27 22:48:24 +03:00

tests

fix(harbor): guarantee CPU for redis sentinels

2026-07-27 22:48:24 +03:00

Chart.yaml

[harbor] Add managed Harbor container registry application

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

Makefile

test(harbor): add helm-unittest coverage for bucket-secret guards

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

values.yaml

fix(harbor): merge BucketInfo at values root, drop targetPath

2026-04-30 09:35:14 +05:00