Another Domain as configured in external_url for some project context
guenther.wagner@...
We are using harbor version 2.5.1, Real cool tool. Actually we wanted shorten the url for some project context and access it with another domain. For general access we use the domain configured from the setting external_url, For the shorten url we put a reverse proxy in front of the harbor instance. Example: Original URL: harbor.company.com/proxy/{docker image name}:{tag} , external_url setting is harbor.company.com Is there a way to support this use case? |
|||||||||
|
|||||||||
Re: 🎉🎉Harbor Release v2.6.0 Highlights🎉🎉
Congrats to the team! One thing I noticed in the blog post: under known limitations there is a number that I believe references an issue, but there is no link there (while in other cases issue references are links). Looking forward to upgrading! (On that note: do you have an estimated timeline for supporting 2.6 in the operator?) Cheers, Mark Orlin Vasilev <orlin@...> ezt írta (időpont: 2022. szept. 28., Sze, 16:17):
|
|||||||||
|
|||||||||
🎉🎉Harbor Release v2.6.0 Highlights🎉🎉
Orlin Vasilev
🎉 Hello Community, In case you have missed the release of v2.6.0 you can find the highlights of it here: https://goharbor.io/blog/harbor-2.6/ You can find everything you need in the release notes. Special HUGE thanks to all new contributors: 🎉🎉🎉
... and of course to everyone involved in that milestone! If you have any questions or requests feel free to reach us in slack or over mail! Orlix Harbor Community Manager |
|||||||||
|
|||||||||
Disable Anonymous access setting in system settings not working at all (Urgent)
gandhi07naren@...
Hello,
We are currently facing a major issue in our Harbor deployment.
Our current version is Harbor v2.2.0
A quick response will be much appreciated and we will be thankful for.
|
|||||||||
|
|||||||||
Re: Amozon s3 for registry
Ignazio Cassano
Some updates: if s3 is behind a proxy I have to add charmusem under Proxy Components. This solves. Ignazio Il giorno gio 22 set 2022 alle ore 14:51 Ignazio Cassano via lists.cncf.io <ignaziocassano=gmail.com@...> ha scritto:
|
|||||||||
|
|||||||||
Re: Amozon s3 for registry
Ignazio Cassano
More updates: seems something is not configured web because in chartmuseum log I get: Get \"https://s3.eu-central-1.amazonaws.com/ignaharbor?prefix=igna\": dial tcp 52.219.168.115:443: i/o timeout","repo":"igna","reqID":"1bcc32aa-6e6c-43a7-a6a6-e3a2b63c2ec3"} igna is the project I created on harbor gui where I can push images but I cannot browse via web interface. Where are my mistakes ? Ignazio Il giorno gio 22 set 2022 alle ore 14:43 Ignazio Cassano via lists.cncf.io <ignaziocassano=gmail.com@...> ha scritto:
|
|||||||||
|
|||||||||
Re: Amozon s3 for registry
Ignazio Cassano
Hello, I do not understand what is rootdirectory. I used the following setup in s3:region: eu-central-1 bucket: ignaharbor accesskey: accesskey secretkey: secret regionendpoint: https://s3.eu-central-1.amazonaws.com The result is I can push images but I cannot browse the project on the harbor web gui.. I can only browse the default "library" project" Please, help me Ignazio Il giorno gio 22 set 2022 alle ore 01:13 daojunz via lists.cncf.io <daojunz=vmware.com@...> ha scritto:
|
|||||||||
|
|||||||||
Re: Error pushing images
Ignazio Cassano
Hello, some updates: it works if I force a GC Il giorno gio 22 set 2022 alle ore 12:42 Ignazio Cassano via lists.cncf.io <ignaziocassano=gmail.com@...> ha scritto:
|
|||||||||
|
|||||||||
Error pushing images
Ignazio Cassano
Hello Everyone, After the first installation of harbor with an external redis and an external DB and with registry on S3, I pushed an images alpine:latest Then I removed harbor and installed it again. I tried to push again the same image and I got: unknown: http status code: 404, body: {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown","detail":{"Name":"primoproj/alpine","Revision":"sha256:1304f174557314a7ed9eddb4eab12fed12cb0cd9809e4c28f29af86979a3c870"}}]} If I try to push a new image that I never pushed before, it works. Any help, please ? Ignazio |
|||||||||
|
|||||||||
Re: Amozon s3 for registry
Ignazio Cassano
Many thanks Ignazio
|
|||||||||
|
|||||||||
Re: Amozon s3 for registry
daojunz
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@...> Hello, I would like to use S3 for registry. In values.yaml of harbor I wrote:
region: eu-central-1
Is this enough to work ?
Thanks Ignazio
|
|||||||||
|
|||||||||
Terraform Harbor Provider looking for maintainers
Orlin Vasilev
Hi all :) As you may know we have adopted https://github.com/goharbor/terraform-provider-harbor In that issue we are asking for help if you are feeling like sparing some time and you know terraform or you want to use that to learn terraform and to join our project in general :) Please reach out to us so we can work on this one together! Orlix Harbor Community Manager |
|||||||||
|
|||||||||
Re: Amozon s3 for registry
Ignazio Cassano
Hello, I tried to push an image but in registry logs, it give me the following error: Il giorno mer 21 set 2022 alle ore 16:42 Ignazio Cassano via lists.cncf.io <ignaziocassano=gmail.com@...> ha scritto:
|
|||||||||
|
|||||||||
Amozon s3 for registry
Ignazio Cassano
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 |
|||||||||
|
|||||||||
Re: harbor multi site
Ignazio Cassano
Thanks for your answer. Please, could you explain a fallback scenario ? Ignazio Il giorno mar 20 set 2022 alle ore 10:39 Vadim Bauer via lists.cncf.io <vb=container-registry.com@...> ha scritto:
|
|||||||||
|
|||||||||
Re: harbor multi site
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. |
|||||||||
|
|||||||||
harbor multi site
Ignazio Cassano
Hello Everyone, I would like to install 3 harbor each one on a different site: harbor 1 on Site A, harbor 2 on Site B and harbor 3 on Site C. To keep them aligned I would like to use harbor replication but only one can push. I wonder if an haproxy load balancer can check which harbor installation is pushing (so which is the master). This because the master could fail and I could switch one of the 2 remained in pushing mode. Thanks Ignazio |
|||||||||
|
|||||||||
Re: goharbor
Ignazio Cassano
Hello, thanks for your answer The following are my values for external redis: external: # 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: "" Il giorno lun 19 set 2022 alle ore 13:25 Orlin Vasilev <orlin@...> ha scritto:
|
|||||||||
|
|||||||||
Re: goharbor
Ignazio Cassano
Hello, thanks for your answer. The following are the redix external values: external: # 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: "" Il giorno lun 19 set 2022 alle ore 13:58 Wenkai Yin <yinw@...> ha scritto:
|
|||||||||
|
|||||||||
Re: goharbor
yinw
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@...> Hi 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:
|
|||||||||
|