forked from goharbor/harbor
-
Notifications
You must be signed in to change notification settings - Fork 0
Home
MinerYang edited this page Sep 11, 2023
·
10 revisions
There's a known issue that upstream distribution(util v2.8.2)do not support redis auth via username-password. See more details issues-18892
This issue would not affect harbor functionalities, such as image pull/push, scan, or GC, but would have minor impact on distribution push/pull performance, especially for cloud storage like s3, when you are using external redis and configured a username. So if you care about the registry performance, please follow the guidance to set up your Redis server that allow you to bypass this limitation, otherwise you could just ignore it.
you need guarantee that requirepass
set up in the redis.conf is same as the password set for acl user, and could connect to redis server successfully.
## redis.conf
requirepass:foobar
## set user password same as requirepass
acl setuser virginia >foobar
## test connection
redis-cli -h <host> -p 6379 -a foobar
10.**.**.**:6379> ping
PONG
redis-cli -h <host> -p 6379 --user virginia --pass foobar
10.**.**.**:6379> ping
PONG