You could refer this configure file
https://github.com/distribution/distribution/blob/main/docs/configuration.md
s3:
accesskey: awsaccesskey
secretkey: awssecretkey
region: us-west-1
regionendpoint: http://myobjects.local
forcepathstyle: true
accelerate: false
bucket: bucketname
encrypt: true
keyid: mykeyid
secure: true
v4auth: true
chunksize: 5242880
multipartcopychunksize: 33554432
multipartcopymaxconcurrency: 100
multipartcopythresholdsize: 33554432
rootdirectory: /s3/object/name/prefix
usedualstack: false
The option in red text is mandatory
Best regards,
Stone (张道军)
Software Engineer, CNA, VMware R&D
--
From:
harbor-users@... <harbor-users@...> on behalf of Ignazio Cassano via lists.cncf.io <ignaziocassano=gmail.com@...>
Date: Wednesday, September 21, 2022 at 10:42 PM
To: harbor-users@... <harbor-users@...>
Subject: [harbor-users] Amozon s3 for registry
Hello,
I would like to use S3 for registry.
In values.yaml of harbor I wrote:
region: eu-central-1
bucket: ignaharbor
accesskey: myaccesskey
secretkey: mysecret
Is this enough to work ?
Thanks
Ignazio
Hello,I would like to use S3 for registry.In values.yaml of harbor I wrote:region: eu-central-1
bucket: ignaharbor
accesskey: myaccesskey
secretkey: mysecretIs this enough to work ?ThanksIgnazio
It's possible to use replication as a way to back up images, but in practice it is not usable.
The main reason is that when you switch sites, you would need to rotate all pull secrets for every consumer of your registry.
A usable fallback scenario is a bit more complicated than that and depends on the given infrastructure.
It's possible to use replication as a way to back up images, but in practice it is not usable.
The main reason is that when you switch sites, you would need to rotate all pull secrets for every consumer of your registry.
A usable fallback scenario is a bit more complicated than that and depends on the given infrastructure.
# support redis, redis+sentinel
# addr for redis: <host_redis>:<port_redis>
# addr for redis+sentinel: <host_sentinel1>:<port_sentinel1>,<host_sentinel2>:<port_sentinel2>,<host_sentinel3>:<port_sentinel3>
addr: "haproxy-harbor:6379"
# The name of the set of Redis instances to monitor, it must be set to support redis+sentinel
sentinelMasterSet: ""
# The "coreDatabaseIndex" must be "0" as the library Harbor
# used doesn't support configuring it
coreDatabaseIndex: "0"
jobserviceDatabaseIndex: "1"
registryDatabaseIndex: "2"
chartmuseumDatabaseIndex: "3"
trivyAdapterIndex: "5"
password: "password"
# If using existingSecret, the key must be REDIS_PASSWORD
existingSecret: ""
Hi Ignazio,can you share a bit more for your values.yaml please you can remove the password and hostnames if you want :)OrlixOn Tue, Sep 6, 2022 at 1:15 PM Ignazio Cassano <ignaziocassano@...> wrote:![]()
Ignazio Cassano via lists.cncf.io <ignaziocassano=gmail.com@...>
12:06 (9 minuti fa)
Hello All,I am trying to setup goarbor with external redis but it does not work:2022-09-06T10:01:34Z [ERROR] [/lib/cache/cache.go:114]: failed to ping redis://redis:xxxxx@haproxy-harbor:6379/0?idle_timeout_seconds=30, retry after 10s : WRONGPASS invalid username-password pair or user is disabled.The password I inserted in values.yaml is correct but seems user is hardcoded.Please, help meIgnazio
# support redis, redis+sentinel
# addr for redis: <host_redis>:<port_redis>
# addr for redis+sentinel: <host_sentinel1>:<port_sentinel1>,<host_sentinel2>:<port_sentinel2>,<host_sentinel3>:<port_sentinel3>
addr: "haproxy-harbor:6379"
# The name of the set of Redis instances to monitor, it must be set to support redis+sentinel
sentinelMasterSet: ""
# The "coreDatabaseIndex" must be "0" as the library Harbor
# used doesn't support configuring it
coreDatabaseIndex: "0"
jobserviceDatabaseIndex: "1"
registryDatabaseIndex: "2"
chartmuseumDatabaseIndex: "3"
trivyAdapterIndex: "5"
password: "********"
# If using existingSecret, the key must be REDIS_PASSWORD
existingSecret: ""
Hi lgnazio, this is a known issue and already fixed. The fix should be available in the next patch release v1.10.1 of Harbor helm chart, or you can patch the Harbor helm chart with the same change in the fix.
Regards,
Wenkai
From: harbor-users@... <harbor-users@...> on behalf of Orlin Vasilev via lists.cncf.io <orlin=orlix.org@...>
Date: Monday, September 19, 2022 at 19:25
To: harbor-users@... <harbor-users@...>
Subject: Re: [harbor-users] goharborHi Ignazio,
can you share a bit more for your values.yaml please you can remove the password and hostnames if you want :)
Orlix
On Tue, Sep 6, 2022 at 1:15 PM Ignazio Cassano <ignaziocassano@...> wrote:
Ignazio Cassano via lists.cncf.io <ignaziocassano=gmail.com@...>
12:06 (9 minuti fa)
Hello All,
I am trying to setup goarbor with external redis but it does not work:
2022-09-06T10:01:34Z [ERROR] [/lib/cache/cache.go:114]: failed to ping redis://redis:xxxxx@haproxy-harbor:6379/0?idle_timeout_seconds=30, retry after 10s : WRONGPASS invalid username-password pair or user is disabled.
The password I inserted in values.yaml is correct but seems user is hardcoded.
Please, help me
Ignazio
Hi lgnazio, this is a known issue and already fixed. The fix should be available in the next patch release v1.10.1 of Harbor helm chart, or you can patch the Harbor helm chart with the same change in the fix.
Regards,
Wenkai
From:
harbor-users@... <harbor-users@...> on behalf of Orlin Vasilev via lists.cncf.io <orlin=orlix.org@...>
Date: Monday, September 19, 2022 at 19:25
To: harbor-users@... <harbor-users@...>
Subject: Re: [harbor-users] goharbor
Hi Ignazio,
can you share a bit more for your values.yaml please you can remove the password and hostnames if you want :)
Orlix
Ignazio Cassano via lists.cncf.io <ignaziocassano=gmail.com@...>
12:06 (9 minuti fa)
Hello All,
I am trying to setup goarbor with external redis but it does not work:
2022-09-06T10:01:34Z [ERROR] [/lib/cache/cache.go:114]: failed to ping redis://redis:xxxxx@haproxy-harbor:6379/0?idle_timeout_seconds=30, retry after 10s : WRONGPASS invalid username-password pair or user is disabled.
The password I inserted in values.yaml is correct but seems user is hardcoded.
Please, help me
Ignazio
![]()
Ignazio Cassano via lists.cncf.io <ignaziocassano=gmail.com@...>
12:06 (9 minuti fa)
Hello All,I am trying to setup goarbor with external redis but it does not work:2022-09-06T10:01:34Z [ERROR] [/lib/cache/cache.go:114]: failed to ping redis://redis:xxxxx@haproxy-harbor:6379/0?idle_timeout_seconds=30, retry after 10s : WRONGPASS invalid username-password pair or user is disabled.The password I inserted in values.yaml is correct but seems user is hardcoded.Please, help meIgnazio
|
12:06 (9 minuti fa)
|
|
Hi all,Well, we know Friday is not the best day for updates but we have some fixes that need your attention :)Release 2.5.2 is out and you can check all changes and updates here:Thank you for all Issues/PR/Slack messages and contributions in general!Especially to :wy65701436chlinsstonezdjOrlixHarbor Community ManagerHappy upgrading!...or maybe on Monday
Hi All,Reminder that CfP is closing on 27th of May:Please submit your talks before that!If you need any help with submitting or you need a stage buddy I'm here to help!I'll be super happy to join everyone on stage or support you in your talk in any way!The benefits of having a talk:- free ticket for KubeCon- recognized as Speaker - special swag/media/parties- make yourself more recognizable- meet one of the best in the fieldetc..I think we have a LOT to show at such a conference so please think about it and drop a line!If nobody files a talk I'll do one! We must be there as a community! :)OrlixHarbor Community Manager
Hi Orlix,
the issue is also opened here: https://github.com/goharbor/harbor/issues/16718.
Greetings,
Gábor
Sent: Wednesday, April 20, 2022 10:04
To: harbor-users@...
Subject: Re: [harbor-users] Failing to push OCI image index with two identical manifests
Szia Gábor,
can you open issue here: https://github.com/goharbor/harbor/issues
as well :)
so others can participate and we can have a bit more readable conversation :)
Orlix
Harbor Community Manager