Open rochaporto opened 3 years ago
@rochaporto How about setup two separated Harbor instances and set replication rule between them?
Thanks @ywk253100 . That would work, but that would still mean duplicating the images right?
This is not going to be in our roadmap anytime soon unfortunately. part of the limitation is due to the underlying docker distribution
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.
Hello, I wanted to know if this issue would be more relevant for the roadmap now in 2023. I have a similar need but I don't want to setup two Harbor.
Hello, Is there any chance of Harbor supporting different storage backend per project for late 2023 or perhaps for 2024 roadmap? I have a similar needs and use case. Currently I have setup multiple Harbors to meet the requirement/regulation but it's just too much waste of resource when you are talking about 100s or even 10s of these setups.
Harbor supports multiple storage backends (s3, swift, filesystem, etc) but this is a global definition applying to all projects.
There are use cases where it would be useful to configure a different backend per project. Examples:
We have a concrete use case for 1. where we already push the images to a shared filesystem using a webhook on the project, but we end up duplicating the images in both S3 and this filesystem.