search

goharbor / harbor

An open source trusted cloud native registry project that stores, signs, and scans content.
https://goharbor.io
Apache License 2.0
24.14k stars 4.76k forks source link

Support for Multiple Destination Registry recipients in "Replication Rules" #14049

Open DandyDeveloper opened 3 years ago

DandyDeveloper commented 3 years ago

Is your feature request related to a problem? Please describe. I have numerous replica Harbor registries globally, I want to easily specify duplicate replica logic for these replicas.

Describe the solution you'd like Currently, the replications rules are 1 destination per rule.

I think it would be ideal to allow for multiple destination registries, assume the defined registries are of the same type.

Describe the main design/architecture of your solution I think this is a relatively simple request, but the workflow would be:

Registry A (Harbor) Registry B (Harbor) Registry C (Docker Registry)

Replication Rules -> New Replication Rule -> Destination registry(ies) -> Dropdown becomes a list of clickable elements.

The first element you select should effectively set a filter so only the SAME registry destination types should be viewable.

I.E. If I select Registry A, Registry C should not be available in that list.

Describe the development plan you've considered TBA

Additional context Add any other context or screenshots about the feature request here.

xaleeks commented 3 years ago

Can you explain what is the limitation with the current approach?

DandyDeveloper commented 3 years ago

@xaleeks It's extremely slow (for the user to do it 1 by 1) and when you have 20 clusters with their own replicas all over the place. Configuring them 1 by 1 as a single entity is horrendous.

github-actions[bot] commented 2 years ago

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.